Get JSON SchemaBundle
Identifierhttps://schemas.sourcemeta.com/modelcontextprotocol/2025-06-18/schema.json
Base DialectDraft7
Dialecthttp://json-schema.org/draft-07/schema#
Health
78%
Size0.079144 MB
Loading schema...

This schema has 0 direct dependencies and 0 indirect dependencies.

This schema has 135 quality errors.

/definitions/AudioContent/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/AudioContent/properties/annotations/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/AudioContent/properties/type/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/BlobResourceContents/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/BooleanSchema/properties/type/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/CallToolRequest/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/CallToolRequest/properties/params/properties/arguments/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/CallToolResult/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/CallToolResult/properties/structuredContent/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/CancelledNotification/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/CancelledNotification/properties/params/properties/requestId/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/ClientCapabilities/properties/elicitation/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/ClientCapabilities/properties/elicitation/propertiesproperties_default

Setting the `properties` keyword to the empty object does not add any further constraint

/definitions/ClientCapabilities/properties/experimental/additionalProperties/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/ClientCapabilities/properties/experimental/additionalProperties/propertiesproperties_default

Setting the `properties` keyword to the empty object does not add any further constraint

/definitions/ClientCapabilities/properties/sampling/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/ClientCapabilities/properties/sampling/propertiesproperties_default

Setting the `properties` keyword to the empty object does not add any further constraint

/definitions/CompleteRequest/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/CompleteResult/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/CreateMessageRequest/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/CreateMessageRequest/properties/params/properties/includeContext/enumenum_with_type

Setting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types

/definitions/CreateMessageRequest/properties/params/properties/metadata/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/CreateMessageRequest/properties/params/properties/metadata/propertiesproperties_default

Setting the `properties` keyword to the empty object does not add any further constraint

/definitions/CreateMessageRequest/properties/params/properties/modelPreferences/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/CreateMessageResult/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/ElicitRequest/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/ElicitRequest/properties/params/properties/requestedSchema/properties/type/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/ElicitResult/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/ElicitResult/properties/action/enumenum_with_type

Setting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types

/definitions/EmbeddedResource/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/EmbeddedResource/properties/annotations/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/EmbeddedResource/properties/type/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/EnumSchema/properties/type/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/GetPromptRequest/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/GetPromptResult/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/ImageContent/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/ImageContent/properties/annotations/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/ImageContent/properties/type/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/InitializeRequest/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/InitializeResult/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/InitializedNotification/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/InitializedNotification/properties/params/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/InitializedNotification/properties/params/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/JSONRPCError/properties/jsonrpc/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/JSONRPCNotification/properties/jsonrpc/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/JSONRPCNotification/properties/params/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/JSONRPCNotification/properties/params/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/JSONRPCRequest/properties/jsonrpc/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/JSONRPCRequest/properties/params/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/JSONRPCRequest/properties/params/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/JSONRPCRequest/properties/params/properties/_meta/properties/progressToken/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/JSONRPCResponse/properties/jsonrpc/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/ListPromptsRequest/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/ListPromptsResult/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/ListResourceTemplatesRequest/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/ListResourceTemplatesResult/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/ListResourcesRequest/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/ListResourcesResult/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/ListRootsRequest/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/ListRootsRequest/properties/params/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/ListRootsRequest/properties/params/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/ListRootsRequest/properties/params/properties/_meta/properties/progressToken/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/ListRootsResult/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/ListToolsRequest/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/ListToolsResult/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/LoggingLevel/enumenum_with_type

Setting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types

/definitions/LoggingMessageNotification/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/LoggingMessageNotification/properties/params/properties/level/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/Notification/properties/params/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/Notification/properties/params/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/NumberSchema/properties/type/enumenum_with_type

Setting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types

/definitions/PaginatedResult/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/PingRequest/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/PingRequest/properties/params/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/PingRequest/properties/params/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/PingRequest/properties/params/properties/_meta/properties/progressToken/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/ProgressNotification/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/ProgressNotification/properties/params/properties/progressToken/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/Prompt/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/PromptListChangedNotification/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/PromptListChangedNotification/properties/params/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/PromptListChangedNotification/properties/params/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/PromptReference/properties/type/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/ReadResourceRequest/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/ReadResourceResult/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/Request/properties/params/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/Request/properties/params/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/Request/properties/params/properties/_meta/properties/progressToken/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/Resource/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/Resource/properties/annotations/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/ResourceContents/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/ResourceLink/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/ResourceLink/properties/annotations/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/ResourceLink/properties/type/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/ResourceListChangedNotification/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/ResourceListChangedNotification/properties/params/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/ResourceListChangedNotification/properties/params/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/ResourceTemplate/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/ResourceTemplate/properties/annotations/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/ResourceTemplateReference/properties/type/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/ResourceUpdatedNotification/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/Result/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/Result/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/Role/enumenum_with_type

Setting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types

/definitions/Root/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/RootsListChangedNotification/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/RootsListChangedNotification/properties/params/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/RootsListChangedNotification/properties/params/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/ServerCapabilities/properties/completions/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/ServerCapabilities/properties/completions/propertiesproperties_default

Setting the `properties` keyword to the empty object does not add any further constraint

/definitions/ServerCapabilities/properties/experimental/additionalProperties/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/ServerCapabilities/properties/experimental/additionalProperties/propertiesproperties_default

Setting the `properties` keyword to the empty object does not add any further constraint

/definitions/ServerCapabilities/properties/logging/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/ServerCapabilities/properties/logging/propertiesproperties_default

Setting the `properties` keyword to the empty object does not add any further constraint

/definitions/SetLevelRequest/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/SetLevelRequest/properties/params/properties/level/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/StringSchema/properties/format/enumenum_with_type

Setting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types

/definitions/StringSchema/properties/type/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/SubscribeRequest/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/TextContent/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/TextContent/properties/annotations/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/TextContent/properties/type/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/TextResourceContents/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/Tool/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/Tool/properties/annotations/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/Tool/properties/inputSchema/properties/properties/additionalProperties/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/Tool/properties/inputSchema/properties/properties/additionalProperties/propertiesproperties_default

Setting the `properties` keyword to the empty object does not add any further constraint

/definitions/Tool/properties/inputSchema/properties/type/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/Tool/properties/outputSchema/properties/properties/additionalProperties/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/Tool/properties/outputSchema/properties/properties/additionalProperties/propertiesproperties_default

Setting the `properties` keyword to the empty object does not add any further constraint

/definitions/Tool/properties/outputSchema/properties/type/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/ToolListChangedNotification/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/ToolListChangedNotification/properties/params/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/ToolListChangedNotification/properties/params/properties/_meta/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/UnsubscribeRequest/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type