Simpler.Asia

studio.reframe_scene

Re-frame one scene for a different aspect ratio: re-centres and scales the EXISTING footage on a focus point (no new pixels; needs the source dimensions). FREE (platform geometry, no provider). New edges (outpainting) are not offered.

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>",
      "target_aspect": "<target_aspect>"
    },
    "name": "studio.reframe_scene"
  }
}

Input Schema

Name	Required	Description	Default
`method`	No	analytic = crop/scale the existing footage (the one method).	analytic
`focus_x`	No	Focus point across the frame, 0-1.
`focus_y`	No	Focus point down the frame, 0-1.
`scene_id`	Yes	Scene to re-frame.
`project_id`	Yes	The studio project (vp_…) this tool acts on.
`target_aspect`	Yes	Aspect to frame for.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 31, 2026

changedInput schema / properties / focus_x / description

Previous value: -"Focus point across the frame, 0-1 (analytic only)."New value: +"Focus point across the frame, 0-1."

changedInput schema / properties / focus_y / description

Previous value: -"Focus point down the frame, 0-1 (analytic only)."New value: +"Focus point down the frame, 0-1."

changedInput schema / properties / method / description

Previous value: -"analytic = crop/scale existing footage; generative = outpaint new edges."New value: +"analytic = crop/scale the existing footage (the one method)."

changedInput schema / properties / method / enum

Previous value: -[
-  "analytic",
-  "generative"
-]New value: +[
+  "analytic"
+]

removedInput schema / properties / prompt

Removed value: -{
-  "description": "What the new edges should contain (generative only).",
-  "type": "string"
-}

First observedOct 23, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations only say readOnlyHint=false, so the description usefully adds that this is a mutation with zero provider cost, purely geometric, and non-generative. It does not say whether the original scene is replaced or a new version is created, nor whether the change is undoable — relevant gaps for a write tool.

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?

One front-loaded sentence with the core action first and qualifiers after; the parentheticals are dense but each carries real information (no new pixels, source dimensions needed, free). Slightly overloaded for a single sentence.

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 6-parameter mutation tool with no output schema, the description covers cost, mechanism, prerequisite, and scope limits. The remaining gap is the effect on existing scene state (in-place edit vs. new version) and failure behavior when source dimensions are unavailable.

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 100%, so the baseline is 3. The description's mention of a 'focus point' and 'source dimensions' ties loosely to focus_x/focus_y and validates the analytic method, but adds no format or default guidance beyond the schema.

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?

Specific verb+resource ('Re-frame one scene') with scope ('different aspect ratio') and a precise mechanical definition: re-centres and scales EXISTING footage on a focus point. It explicitly rules out generating pixels and rules out outpainting, which cleanly separates it from siblings like studio.generate_scene.

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?

States an explicit exclusion ('New edges (outpainting) are not offered') and a prerequisite ('needs the source dimensions'), plus the cost profile ('FREE, no provider'). It stops short of naming the sibling to use when outpainting is wanted, so the agent must infer the alternative.

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?