Skip to main content
MCP tools are grouped by workflow. Tool names are stable enough for client configuration and prompting, but clients should still read each tool schema at runtime.

Read-only and mutating tools

Read-only tools inspect state or search supported inputs. Mutating tools create, edit, deploy, or stop resources in the authenticated account. Use MCP only in clients you trust with account access. Ask your MCP client to confirm mutating calls before execution, and do not approve deploy or stop actions unless you initiated them. This is especially important for build_blueprint, deploy_blueprint, and stop_blueprint.

Blueprint management

ToolScopeMutatesKey argumentsPurpose
list_blueprintsblueprints:readNononeList blueprints owned by the authenticated account
get_blueprint_stateblueprints:readNoblueprint_idRead nodes, connections, layout, and deployment status
create_blueprintblueprints:writeYesnameCreate an empty blueprint
rename_blueprintblueprints:writeYesblueprint_id, nameRename an existing blueprint

Blueprint editing

ToolScopeMutatesKey argumentsPurpose
describe_node_typesnoneNooptional node type filtersDiscover supported building blocks and expected inputs
validate_blueprintblueprints:readNoblueprint_idCheck a blueprint for structural and configuration issues
add_nodeblueprints:writeYesblueprint_id, type, configAdd a building block to a blueprint
configure_nodeblueprints:writeYesblueprint_id, node_id, configUpdate a building block configuration
connect_nodesblueprints:writeYesblueprint_id, source and target node IDsConnect two existing building blocks
delete_nodeblueprints:writeYesblueprint_id, node_idRemove a building block and its connections
build_blueprintblueprints:writeYesblueprint_id, nodes, edgesAdd multiple building blocks and connections in one request
auto_layoutblueprints:writeYesblueprint_idArrange a blueprint visually
ToolScopeMutatesKey argumentsPurpose
search_marketsnoneNoquery or market slugSearch Polymarket markets
search_stocksnoneNoquerySearch supported stock symbols
search_forex_pairsnoneNoquerySearch supported forex pairs

Live controls

ToolScopeMutatesKey argumentsPurpose
deploy_blueprintblueprints:deployYesblueprint_idStart a reviewed blueprint
stop_blueprintblueprints:deployYesblueprint_idStop a running blueprint
  1. Call list_blueprints or create_blueprint.
  2. Call get_blueprint_state before editing an existing blueprint.
  3. Call describe_node_types when the client needs available building blocks.
  4. Use editing tools to make the change.
  5. Call validate_blueprint.
  6. Review the result before calling deploy_blueprint.

Prompting pattern

For safer edits, ask the client to separate planning from execution:
Inspect this blueprint, explain the exact edits you plan to make, then wait for my approval before calling any mutating tools.
For deployment:
Validate the blueprint and summarize any warnings. Do not deploy until I explicitly approve.