Class McpToolSchema
Instances expose derived, fixed, and application-authored input schemas
for inspection, but applications cannot construct or replace this type
directly. Programmatic tool registrations may provide an authored Profile 1
object-root input document through
McpToolRegistration.ArgumentTypeStage.inputSchema(McpJsonObject);
output schemas remain derived. Profile 1 is a closed generation and
validation profile based on JSON Schema Draft 2020-12, not a complete Draft
2020-12 implementation.
Evaluation has independent resource bounds, including one million operations and 128 active evaluation calls. A value within the JSON byte, depth and node limits can still exhaust schema evaluation. Repeated applicators, reference traversals, equality checks and object-member sorting contribute work; satisfying the schema semantically does not guarantee completion within these bounds. Limit exhaustion rejects input through the revision's ordinary tool-validation result, and output through the fixed internal-error result. Internal diagnostics are not exposed on the wire.
- Author:
- Mark Allen
-
Method Summary
Modifier and TypeMethodDescriptionbooleanReturns the preserved schema document published on the MCP wire.inthashCode()
-
Method Details
-
getDocument
Returns the preserved schema document published on the MCP wire.- Returns:
- immutable schema object
-
equals
-
hashCode
-