Studio
The Studio MCP tools: `contract_presets`.
The Studio category has 1 tool:
contract_presets— List every contract the studio can generate, with each preset's parameters, their types and defaults, the OpenZeppelin files it is built on, its licence, its wizard feature flags, and its audit label. Takes no arguments, is public, and is FREE. Call it before generating anything:paramsis per-preset and the order is the constructor's order, so the catalogue is the only place to read a preset's shape from — a required parameter that is missing is refused naming it, and an optional one falls back to its declared default.auditis the label the deploy path will enforce for a CLEAN generation of that preset, and it is a label on putty's own template, not an external audit of anything. This tool does not generate anything. Generation is a metered operation and the MCP surface does not expose it: a tool that spends credits has to be gated by a run's approval, and a direct tool call has no run to gate. Ask the person to run the deploy path, which prices the generate, the compile, and the tests together.
The full request and response shape for each, and a live playground, live on the generated reference at GET /mcp/tools.
Contracts
The Contract & Hook Studio's preset catalogue, with each preset's parameters, defaults, and audit label.
contract_presets
List every contract the studio can generate, with each preset's parameters, their types and defaults, the OpenZeppelin files it is built on, its licence, its wizard feature flags, and its audit label. Takes no arguments, is public, and is FREE. Call it before generating anything: `params` is per-preset and the order is the constructor's order, so the catalogue is the only place to read a preset's shape from — a required parameter that is missing is refused naming it, and an optional one falls back to its declared default. `audit` is the label the deploy path will enforce for a CLEAN generation of that preset, and it is a label on putty's own template, not an external audit of anything. **This tool does not generate anything.** Generation is a metered operation and the MCP surface does not expose it: a tool that spends credits has to be gated by a run's approval, and a direct tool call has no run to gate. Ask the person to run the deploy path, which prices the generate, the compile, and the tests together.