Simpler.Asia

studio.style_transfer

[$0.336/sec at provider cost] Restyle a scene's footage, keeping its motion. style must be one of the presets (anime, comic, watercolor, oil_painting, sketch, cinematic, vintage, neon). A free-text style is refused, because free text over the user's footage could change who appears in it; pick the closest preset instead. Mints a NEW asset - the original is never destroyed.

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>",
      "style": "<style>"
    },
    "name": "studio.style_transfer"
  }
}

Input Schema

Name	Required	Description
`style`	Yes	A preset key: anime, comic, watercolor, oil_painting, sketch, cinematic, vintage, neon. Free text is refused.
`scene_id`	Yes	Scene whose footage to restyle.
`project_id`	Yes	The studio project (vp_…) this tool acts on.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds substantial context beyond the single readOnlyHint=false annotation: an explicit cost rate ('$0.336/sec at provider cost'), the non-destructive guarantee ('the original is never destroyed'), and the output behavior ('Mints a NEW asset'). The rationale that free-text style could alter who appears in the footage is a meaningful safety disclosure an agent would not otherwise know.

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-loads cost, then the hard constraint, then the side-effect guarantee — good ordering with no filler sentences. Minor redundancy: the eight preset keys are repeated verbatim from the schema enum, and the free-text refusal is stated twice within the same description.

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?

For a costly, non-destructive generation tool with no output schema, the definition covers cost, input restriction, output shape ('mints a NEW asset'), and destructiveness — the four things an agent needs before committing spend.

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 description coverage is 100% and the enum is already declared, so the description's verbatim preset list and the 'free text is refused' note largely restate structured fields. The added value is the safety reason behind the enum restriction, but no new syntax or format detail is contributed; baseline 3 applies.

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 ('Restyle a scene's footage') plus the key invariant ('keeping its motion'), which separates it from the scene-level editing siblings and from image.style_transfer, which operates on images rather than scene footage. An agent can identify the operation without opening the schema.

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 clear in-tool guidance: style must be one of eight presets, free text is refused, and the fallback is 'pick the closest preset instead.' It does not position the tool against nearby alternatives (studio.color_grade, image.style_transfer), so the when-to-use-vs-sibling dimension is left to inference.

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?