Rokha

Adopt a published rig as your own runnable copy

registry_adopt

The select → input → run door: materialize YOUR OWN runnable copy of any published rig listing (find provider_id + external_id via registry_search; the listing must carry a metadata.rig skeleton). Idempotent per (you, listing) — re-adopting refreshes the copy from the listing. Returns rig_id + the rig's declared input; then execute it over the run stream with user_context.rig_id and run_input. Runs bill YOUR allowance, never the creator's. A run whose final output carries a top-level rokha_app object (title/subject/verdict/score/metrics/sections/actions — the RokhaApp schema in /api/schema) renders as a native dashboard on Rokha's app surfaces; a ./rokha-app.html artifact saved by the run renders as its live app. Requires Authorization: Bearer .

Input Schema

Name	Required	Description	Default
`external_id`	Yes	the listing's external_id (e.g. 'rig-template-solwatch-audit')
`provider_id`	Yes	the listing's provider (e.g. 'rokha')

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedSep 26, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Far beyond the annotations: it discloses idempotency keyed to (you, listing), refresh-on-re-adopt semantics, that runs bill the caller's allowance and never the creator's, the required Bearer JWT, and the return shape. No contradiction with readOnlyHint=false / destructiveHint=false — this is clearly a mutating but non-destructive copy operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and dense with the actionable path first, then consequences. The closing sentences about RokhaApp rendering and the ./rokha-app.html artifact describe what happens after a subsequent run rather than what adopt does, so they are somewhat off-topic baggage for this specific tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, yet the description still usefully names what returns (rig_id plus declared input) and how to use it next. For a two-param mutation with auth and billing implications, nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: both identifiers are sourced from registry_search, and external_id only resolves to something adoptable if the listing carries a metadata.rig skeleton. That precondition is not in the schema and materially affects whether the call is worth making.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'materialize YOUR OWN runnable copy of any published rig listing.' The 'select → input → run door' framing plus the named listing identifiers let an agent distinguish this from registry_search, rig_get, and rig_run without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: get provider_id + external_id via registry_search, requires the listing to carry a metadata.rig skeleton, then execute via the run stream with user_context.rig_id and run_input. It also covers the repeat case — re-adopting is idempotent and refreshes the copy rather than duplicating.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Rokha tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.