Skip to content

The specification generated for enum values does not include the potential values #460

@yinzara

Description

@yinzara

When writing a MCP tool that returns a structured JSON output, the list-tools request returns a model that does not state the possible enum values for the enum. This makes it so the input schema does not know what potentially could be sent for each enum value and what the values represent.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions