Skip to content

Consider always providing schema properties #693

@findleyr

Description

@findleyr

Following up on discussion in github/github-mcp-server#1548, this issue tracks deciding whether we want to always provide an empty "properties" field for schemas. For example could handle this in the jsonschema library for inferred schemas, and/or panic at tool registration time for user-defined schemas.

We should confirm whether "properties" is required by the JSON schema spec (after 5m search, I still don't know). If it is, then the answer is clear that we should enforce it. If not, we still may want to do so for compatibility purposes.

CC @jba

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions