Simpler.Asia

studio.request_regeneration

Flag a generated scene that does not match intent: record WHY and an improved prompt. This stages the improved prompt on the scene (regeneration is a separate paid, user-approved step — it never silently destroys footage or spends).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "scene_id": "<scene_id>",
      "reason": "<reason>",
      "improved_prompt": "<improved_prompt>"
    },
    "name": "studio.request_regeneration"
  }
}

Input Schema

Name	Required	Description
`reason`	Yes	Why it needs regeneration.
`scene_id`	Yes
`project_id`	Yes	The studio project (vp_…) this tool acts on.
`improved_prompt`	Yes	The improved prompt.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With only readOnlyHint=false available, the description carries real weight: it discloses that this only stages a prompt, never silently destroys footage, never spends money, and requires user approval for the downstream step. It does not say whether re-flagging the same scene overwrites a prior staged prompt or how the staging is surfaced.

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

Conciseness5/5

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

Two sentences, no filler, and the key constraint (staging vs. actual regeneration cost/approval) is front-loaded in the second sentence rather than buried. Every clause adds decision-relevant information.

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

Completeness4/5

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

For a small 4-required-param mutation with no output schema, the description covers what gets stored and what deliberately does not happen. The remaining gap is return behavior and whether repeated calls overwrite staged state, which an agent might want to know.

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

Parameters3/5

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

Schema coverage is 75%, so most parameters are already documented. The description reinforces that reason captures why and improved_prompt is the replacement prompt, but adds no format, length, or content guidance beyond the schema text; scene_id remains undetailed in both places.

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 ("Flag a generated scene") plus the exact artifacts it records ("WHY and an improved prompt"), and explicitly separates it from regeneration itself, which is the job of siblings like studio.generate_scene. An agent can distinguish it from studio.update_scene / studio.generate_scene without reading schemas.

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

Usage Guidelines4/5

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

Gives a clear trigger condition ("a generated scene that does not match intent") and a clear exclusion ("regeneration is a separate paid, user-approved step"). It does not name the specific sibling to call for the actual regeneration, so the routing is implied rather than explicit.

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

All Simpler.Asia tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?