ruby-sdk/test/mcp/tool/input_schema_test.rb
Koichi ITO 5ca8b6ebbb Conform Tool Schemas to JSON Schema 2020-12 per SEP-2106
## Motivation and Context

SEP-2106 (modelcontextprotocol/modelcontextprotocol#2106, merged for the 2026-07-28 spec release)
makes tool `inputSchema` and `outputSchema` conform to the full JSON Schema 2020-12 vocabulary:
an input schema keeps `type: "object"` at the root but may use any 2020-12 keyword below it;
an output schema may be ANY valid schema (object, array, primitive, or a root-level composition);
and `CallToolResult.structuredContent` widens from an object to any JSON value. The SEP also adds
resource bounds: `$ref` resolution is restricted (same-document only in the reference implementation) and
composition-heavy documents must be bounded to avoid excessive validation cost.

This follows the TypeScript SDK's reference implementation (typescript-sdk#2249; the Python SDK tracks
the same work in python-sdk#2792):

- `Tool::Schema` now validates against the JSON Schema 2020-12 metaschema rather than the draft-04 metaschema.
  The draft-04 pin was a stopgap from when the SDK used the `json-schema` gem, which did not support 2020-12;
  `json_schemer` does, so `$defs`/`$ref` and the rest of the 2020-12 vocabulary now resolve natively.
  This matches the dialect the SDK already advertises in emitted schemas and the Python SDK's behavior,
   whose `jsonschema.validate` selects the validator from the schema's `$schema`.
- `Tool::Schema` moves root-type defaulting into an overridable `apply_default_root_type!` hook.
  `InputSchema` keeps the historical `type: "object"` default; `OutputSchema` now applies it only
  when no root schema keyword (`type`, `$ref`, `oneOf`, `anyOf`, `allOf`, `not`, `if`, `const`, `enum`) is present.
  The previous unconditional default merged `type: "object"` into root combinators such as `{ oneOf: [...] }`,
  producing a wrong schema, so that case is a bug fix.
- `Tool::Schema` enforces the TypeScript SDK's schema bounds at construction time: only same-document
  `$ref`/`$dynamicRef`s (starting with `#`, so schema handling can never trigger network or file access),
  `MAX_SCHEMA_DEPTH = 64` nesting levels, and `MAX_SUBSCHEMA_COUNT = 10_000` subschema objects,
  all raising `ArgumentError` on violation.
- `Server#call_tool` mirrors non-object `structuredContent` into `content` as serialized JSON text
  when the tool provided no content blocks, so pre-SEP clients that only read `content` still receive the data.
  Object results and explicit content are untouched.

Resolves #377.

## How Has This Been Tested?

- `test/mcp/tool/output_schema_test.rb`: root-level `oneOf`, `$ref`+`$defs`, primitive, and `enum` schemas serialize
  without an injected `type` and validate results correctly; the `properties`-only shorthand still serializes
  with `type: "object"` (wire-format regression); explicit `type: "array"` keeps working.
- `test/mcp/tool/input_schema_test.rb`: an input schema using `$defs`, `$ref`, `oneOf`, `if`/`then`, and `allOf`
  keeps its object root and round-trips all keywords; a draft-04-only boolean `exclusiveMinimum` is rejected
  under the 2020-12 dialect while the numeric form is accepted.
- `test/mcp/tool/schema_test.rb`: depth and subschema-count bound violations raise `ArgumentError`;
  non-same-document `$ref`s (remote URI, sibling file) are rejected while `#/$defs/...` is accepted.
  The previous unbounded-depth caching test is replaced, since the depth bound now rejects such documents by design.
- `test/mcp/server_test.rb`: `tools/call` with array `structuredContent` and no content gains
  the serialized TextContent fallback; explicit content is not overwritten; object `structuredContent` gets no fallback.

`bundle exec rake` (tests, RuboCop, and conformance baseline, including the `json-schema-2020-12` server scenario) passes.

## Breaking Changes

Three narrow behavior changes, all intentional per the SEP:

- Runtime validation now uses the JSON Schema 2020-12 metaschema instead of draft-04.
  Schemas that rely on draft-04-only syntax are rejected at construction time. The practical case is the boolean
  `exclusiveMinimum`/`exclusiveMaximum` form (deprecated since draft-06), which must now be the numeric form;
  the Python SDK rejects it the same way. Other draft-04 spellings (`definitions`, `id`, `dependencies`) still validate,
  since 2020-12 tolerates unknown keywords.
- Schemas that exceed the new resource bounds (nesting deeper than 64, more than 10,000 subschema objects) or
  use a non-same-document `$ref`/`$dynamicRef` now raise `ArgumentError` at construction time.
  Previously such documents were accepted (external references were already never fetched, only ignored).
- An `OutputSchema` whose root declares a schema keyword other than `type` (e.g. `oneOf`) no longer has  `type: "object"`
  merged into it. The old output was an invalid hybrid schema, so no conforming consumer could have relied on it.
2026-06-19 21:36:55 +09:00

261 lines
10 KiB
Ruby

# frozen_string_literal: true
require "test_helper"
module MCP
class Tool
class InputSchemaTest < ActiveSupport::TestCase
test "required arguments are converted to strings" do
input_schema = InputSchema.new(properties: { message: { type: "string" } }, required: [:message])
assert_equal ["message"], input_schema.to_h[:required]
end
test "to_h returns a hash representation of the input schema" do
input_schema = InputSchema.new(properties: { message: { type: "string" } }, required: ["message"])
assert_equal(
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
type: "object",
properties: { message: { type: "string" } },
required: ["message"],
},
input_schema.to_h,
)
end
test "to_h returns a hash representation of the input schema with additionalProperties set to false" do
input_schema = InputSchema.new(properties: { message: { type: "string" } }, required: ["message"], additionalProperties: false)
assert_equal(
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
type: "object",
properties: { message: { type: "string" } },
required: ["message"],
additionalProperties: false,
},
input_schema.to_h,
)
end
test "to_h preserves user-supplied $schema dialect" do
input_schema = InputSchema.new(
"$schema": "https://json-schema.org/draft/2019-09/schema",
properties: { message: { type: "string" } },
)
assert_equal "https://json-schema.org/draft/2019-09/schema", input_schema.to_h[:"$schema"]
end
test "validate_arguments works when user supplies a 2020-12 $schema" do
input_schema = InputSchema.new(
"$schema": "https://json-schema.org/draft/2020-12/schema",
properties: { foo: { type: "string" } },
required: ["foo"],
)
assert_nil(input_schema.validate_arguments(foo: "bar"))
assert_raises(InputSchema::ValidationError) do
input_schema.validate_arguments({ foo: 123 })
end
end
test "to_h preserves user-supplied $schema given via string key" do
# The initializer normalizes input through `JSON.parse(...,
# symbolize_names: true)`, so a string-keyed `"$schema"` should
# arrive at `schema_for_validation` the same as a symbol-keyed one.
input_schema = InputSchema.new(
{
"$schema" => "https://json-schema.org/draft/2020-12/schema",
"properties" => { "foo" => { "type" => "string" } },
"required" => ["foo"],
},
)
assert_equal "https://json-schema.org/draft/2020-12/schema", input_schema.to_h[:"$schema"]
assert_nil(input_schema.validate_arguments(foo: "bar"))
end
test "missing_required_arguments returns an array of missing required arguments" do
input_schema = InputSchema.new(properties: { message: { type: "string" } }, required: ["message"])
assert_equal ["message"], input_schema.missing_required_arguments({})
end
test "missing_required_arguments returns an empty array if no required arguments are missing" do
input_schema = InputSchema.new(properties: { message: { type: "string" } }, required: ["message"])
assert_equal([], input_schema.missing_required_arguments({ message: "Hello, world!" }))
end
test "valid schema initialization" do
schema = InputSchema.new(properties: { foo: { type: "string" } }, required: ["foo"])
assert_equal(
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
type: "object",
properties: { foo: { type: "string" } },
required: ["foo"],
},
schema.to_h,
)
end
test "invalid schema raises argument error" do
assert_raises(ArgumentError) do
InputSchema.new(properties: { foo: { type: "invalid_type" } }, required: ["foo"])
end
end
test "rejects a draft-04-only boolean exclusiveMinimum under the 2020-12 dialect" do
# SEP-2106 validates tool schemas against the JSON Schema 2020-12 metaschema,
# where `exclusiveMinimum` must be a number. The draft-04 boolean form (deprecated since draft-06)
# is rejected at construction, matching the Python SDK's `jsonschema` validator selection.
error = assert_raises(ArgumentError) do
InputSchema.new(properties: { age: { type: "integer", minimum: 0, exclusiveMinimum: true } })
end
assert_includes error.message, "Invalid JSON Schema"
end
test "accepts the 2020-12 numeric exclusiveMinimum form" do
assert_nothing_raised do
InputSchema.new(properties: { age: { type: "integer", exclusiveMinimum: 0 } })
end
end
test "schema without required arguments is valid" do
assert_nothing_raised do
InputSchema.new(properties: { foo: { type: "string" } })
end
end
test "validate arguments with valid data" do
schema = InputSchema.new(properties: { foo: { type: "string" } }, required: ["foo"])
assert_nil(schema.validate_arguments({ foo: "bar" }))
end
test "validate arguments with invalid data" do
schema = InputSchema.new(properties: { foo: { type: "string" } }, required: ["foo"])
assert_raises(InputSchema::ValidationError) do
schema.validate_arguments({ foo: 123 })
end
end
test "validate arguments with valid data when additionalProperties set to nil (default)" do
schema = InputSchema.new(properties: { foo: { type: "string" } }, required: ["foo"])
assert_nil(schema.validate_arguments({ foo: "bar", extra: 123 }))
end
test "validate arguments with valid data when additionalProperties set to true (default)" do
schema = InputSchema.new(properties: { foo: { type: "string" } }, required: ["foo"], additionalProperties: true)
assert_nil(schema.validate_arguments({ foo: "bar", extra: 123 }))
end
test "validate arguments with invalid data when additionalProperties set to false" do
schema = InputSchema.new(properties: { foo: { type: "string" } }, required: ["foo"], additionalProperties: false)
assert_raises(InputSchema::ValidationError) do
schema.validate_arguments({ foo: "bar", extra: 123 })
end
end
test "unexpected errors bubble up from validate_arguments" do
schema = InputSchema.new(properties: { foo: { type: "string" } }, required: ["foo"])
JSONSchemer::Schema.any_instance.stubs(:validate).raises("unexpected error")
assert_raises(RuntimeError) do
schema.validate_arguments(foo: "bar")
end
end
test "accepts schemas with $ref references" do
schema = InputSchema.new(
properties: {
foo: { type: "string" },
},
definitions: {
bar: { type: "string" },
},
required: ["foo"],
)
assert_includes schema.to_h.keys, :definitions
end
test "accepts schemas with $ref string key and includes $ref in to_h" do
schema = InputSchema.new({
"properties" => {
"foo" => { "$ref" => "#/definitions/bar" },
},
"definitions" => {
"bar" => { "type" => "string" },
},
})
assert_equal "#/definitions/bar", schema.to_h[:properties][:foo][:$ref]
end
test "accepts schemas with $ref symbol key and includes $ref in to_h" do
schema = InputSchema.new({
properties: {
foo: { :$ref => "#/definitions/bar" },
},
definitions: {
bar: { type: "string" },
},
})
assert_equal "#/definitions/bar", schema.to_h[:properties][:foo][:$ref]
end
test "keeps the object root type while accepting 2020-12 composition keywords" do
# Per SEP-2106, an input schema root must stay `type: "object"` but may use
# the full 2020-12 vocabulary below the root.
schema = InputSchema.new(
"$defs": { name: { type: "string", minLength: 1 } },
properties: {
name: { "$ref": "#/$defs/name" },
value: { oneOf: [{ type: "string" }, { type: "integer" }] },
},
if: { properties: { value: { type: "integer" } } },
then: { required: ["name"] },
allOf: [{ properties: { extra: { type: "boolean" } } }],
)
assert_equal "object", schema.to_h[:type]
assert schema.to_h.key?(:"$defs")
assert schema.to_h.key?(:if)
assert schema.to_h.key?(:allOf)
end
test "== compares two input schemas with the same properties, required fields" do
schema1 = InputSchema.new(properties: { foo: { type: "string" } }, required: ["foo"])
schema2 = InputSchema.new(properties: { foo: { type: "string" } }, required: ["foo"])
assert_equal schema1, schema2
schema3 = InputSchema.new(properties: { bar: { type: "string" } }, required: ["bar"])
refute_equal schema1, schema3
schema4 = InputSchema.new(properties: { foo: { type: "string" } }, required: ["bar"])
refute_equal schema1, schema4
schema5 = InputSchema.new(properties: { bar: { type: "string" } }, required: ["foo"])
refute_equal schema1, schema5
schema6 = InputSchema.new(properties: { foo: { type: "string" } }, required: ["foo"], additionalProperties: false)
refute_equal schema1, schema6
end
test "format keyword is not enforced (legacy behavior)" do
schema = InputSchema.new(
properties: { email: { type: "string", format: "email" } },
required: ["email"],
)
assert_nil(schema.validate_arguments(email: "not_an_email"))
end
test "invalid pattern raises ArgumentError, not RegexpError" do
error = assert_raises(ArgumentError) do
InputSchema.new(properties: { id: { type: "string", pattern: "[" } })
end
assert_includes error.message, "Invalid JSON Schema"
end
test "Symbol values in arguments are treated as strings" do
schema = InputSchema.new(properties: { foo: { type: "string" } }, required: ["foo"])
assert_nil(schema.validate_arguments(foo: :bar))
end
end
end
end