perf(mcp): advertise each tool JSON Schema once per target (#1059)
The MCP SDK reconverts every registered Zod schema on each tools/list. With 139 tools that is ~45 ms of Zod JSON Schema work per listing, for a catalog that cannot change after registration. Memoize the advertised input and output projections per target on the registration clones. Listings are byte-identical; repeated tools/list drops from ~62 ms to ~18 ms on the stdio server. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
163ee09a74
commit
5ccb9241be
@@ -1,5 +1,8 @@
|
||||
import type { ToolContract } from "../contracts/toolContracts.js";
|
||||
import { toolInputSchemaWithMetadata } from "../contracts/toolSchemaMetadata.js";
|
||||
import {
|
||||
toolInputSchemaWithMetadata,
|
||||
toolOutputSchemaWithMetadata,
|
||||
} from "../contracts/toolSchemaMetadata.js";
|
||||
|
||||
/** Project the canonical Zod contracts directly into SDK registration. */
|
||||
export const toolRegistrationOptions = <Contract extends ToolContract>(
|
||||
@@ -14,6 +17,6 @@ export const toolRegistrationOptions = <Contract extends ToolContract>(
|
||||
title: contract.title,
|
||||
description: contract.description,
|
||||
inputSchema: toolInputSchemaWithMetadata(contract),
|
||||
outputSchema: contract.outputSchema,
|
||||
outputSchema: toolOutputSchemaWithMetadata(contract),
|
||||
annotations: contract.annotations,
|
||||
});
|
||||
|
||||
Reference in New Issue
Block a user