the arguments of the MCP tools the repository serves, in mcp/cas and mcp/evo. A tool's argument schema is both the inputSchema the server advertises, through toJsonSchema, and the check its arguments pass.
A message read from a peer is read with parse: what comes in is rebuilt to the schema. The envelopes say open, so a peer on a later protocol revision can add members (open containers); a tool's arguments are closed, because the server defines that vocabulary.
Examples
The demo on this page offers four schemas: a JSON-RPC request, an MCP tool, and the arguments of cas_add and evo_add, each shown as the import that brings it in and with a value it accepts. They are defined in sample.f.mjs, and the module page's demo lists them among all the others.
Where it is implemented
The modules linked above.
Demo
A JSON-RPC 2.0 request; without an id it is a notification. open(), so a peer on a later protocol revision can add members. Read with parse.