Types and parameter decorator of McpRoute: the tool configuration and
McpRoute.Params.
Evidence
contracts/common.md#principled-implementation Tool metadata retains its definition and default empty-object schema. Params records its argument position and shared checker; successful assert/validate data becomes the tool argument, while errors retain InvalidParams mapping and legacy error-only callbacks retain raw input. The adaptor reads the same metadata field names when registering tools.
Evidence
contracts/common.md#clear-and-simple-design Two decorators and one config type in one namespace, sharing one emplace helper for parameter metadata.
Evidence
contracts/common.md#prohibited-implementation-shortcuts It uses the reflect metadata API and no NestJS internals; the input schema is filled by the generator, not hardcoded here.
Evidence
contracts/common.md#meaningful-documentation The comment documents the two call forms, the configuration fields, and the parameter decorator.
Evidence Exclude
contracts/portability.md#os-neutral-implementation Tool schemas and parameter metadata are protocol data held on controller methods, without native filesystem access.
Types and parameter decorator of McpRoute: the tool configuration and
McpRoute.Params.Evidence
contracts/common.md#principled-implementation Tool metadata retains its definition and default empty-object schema. Params records its argument position and shared checker; successful assert/validate data becomes the tool argument, while errors retain InvalidParams mapping and legacy error-only callbacks retain raw input. The adaptor reads the same metadata field names when registering tools.
Evidence
contracts/common.md#clear-and-simple-design Two decorators and one config type in one namespace, sharing one
emplacehelper for parameter metadata.Evidence
contracts/common.md#prohibited-implementation-shortcuts It uses the reflect metadata API and no NestJS internals; the input schema is filled by the generator, not hardcoded here.
Evidence
contracts/common.md#meaningful-documentation The comment documents the two call forms, the configuration fields, and the parameter decorator.
Evidence Exclude
contracts/portability.md#os-neutral-implementation Tool schemas and parameter metadata are protocol data held on controller methods, without native filesystem access.