Module internal 

The internal tool contracts: name, description, input and output JSON Schemas, whether a built-in implementation exists (mapping-only contracts are code.run, knowledge.*, search.*), and the default grants.

The contract is what callers see, and an override swaps only the implementation behind it. That separation is what lets an operator move a tool onto an MCP server without any caller — model, workflow or subagent — having to be told, and it is why the schemas here are the authority on a tool’s shape rather than whatever a mapped server happens to advertise.

Structs

Contract

One contract.

DefaultGrant

Who may call a tool by default, before configuration widens or narrows it.

Functions

contracts

Every internal contract (deterministic order).

names

The contract names, in table order.