Simpler.Asia

studio.color_grade

Apply color grading to a scene (each channel -100..100; temperature negative = cool, positive = warm).

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

Input Schema

Name	Required	Description
`contrast`	No
`scene_id`	Yes
`brightness`	No
`project_id`	Yes	The studio project (vp_…) this tool acts on.
`saturation`	No
`temperature`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

C2.9/5.0

Behavior2/5

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

The only annotation is readOnlyHint=false, so the description must carry the behavioral burden. It discloses valid ranges and temperature orientation but not whether the grade overwrites an existing grade, whether it is reversible, or what happens to unset channels — important for a mutation tool.

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?

A single front-loaded sentence with no waste; the operation is stated first and the range/semantics parenthetical follows efficiently.

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

Completeness2/5

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

For a mutation tool with no output schema, one weak annotation, and 5 of 6 parameters undocumented, the description is too thin. It omits what the call changes or returns, whether prior grading is replaced, and any permission or locking context.

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 only 17%, so the description must compensate. It adds the -100..100 range and temperature direction (negative cool, positive warm), but does not clarify which parameters are the "channels" (contrast/brightness/saturation) or describe scene_id, leaving part of the gap unfilled.

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

Purpose4/5

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

States a specific verb ("Apply color grading") and resource ("a scene"), so the operation is unambiguous. It does not differentiate itself from adjacent tools like studio.update_scene or studio.style_transfer, but the purpose is clearly conveyed.

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

Usage Guidelines2/5

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

No indication of when to use this versus alternatives such as studio.update_scene, studio.style_transfer, or image.adjust. No prerequisites are stated (scene existence, project scope, or whether a prior grade is replaced).

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?