Clypmint

Note the canvas selection

canvas_select

DestructiveIdempotent

Only the canvas app calls this. Cost: Free.

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": {
      "video_id": "<video_id>",
      "layers": "<layers>",
      "at": "<at>"
    },
    "name": "canvas_select"
  }
}

Input Schema

Name	Required	Description
`at`	Yes	The second the canvas is on.
`layers`	Yes	The layers selected on the canvas.
`video_id`	Yes	Video; the open one if left out.

Output Schema

Name	Required	Description	Default
`code`	No
`cost`	No
`error`	No
`state`	No
`status`	No
`dry_run`	No
`message`	No
`plan_id`	No
`style_id`	No
`video_id`	No
`available`	No
`import_id`	No
`output_id`	No
`studio_url`	No
`version_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026

changedInput schema / properties / video_id / description

Previous value: -"The video; the open one when left out."New value: +"Video; the open one if left out."

AddedNov 6, 2026

TDQS

C2.5/5.0

Behavior2/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, yet the description says nothing about what is destroyed, overwritten, or persisted, and does not flag that a prior selection may be replaced. 'Cost: Free' adds a minor operational note but does not cover the destructive behavior an agent must know about.

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

Conciseness3/5

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

Two short sentences with no bloat, but 'Cost: Free' is filler that does not help an agent decide or invoke correctly, and the one useful sentence (the caller restriction) is not paired with any statement of effect.

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?

The tool takes three required parameters, returns an output schema, and is flagged destructive, yet the description explains none of the consequences of calling it. For a state-changing 'note selection' operation, the description leaves the agent without enough to judge whether calling it is safe.

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%, so video_id, layers, and at are each documented in the schema, including the notable 'the open one if left out' default for video_id. The description adds no meaning beyond that, so the baseline of 3 applies.

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

Purpose2/5

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

The description never states what the tool does. 'Only the canvas app calls this. Cost: Free.' describes a caller and a cost, not a verb+resource action; the purpose is only inferable from the name and title ('Note the canvas selection').

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

Usage Guidelines3/5

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

'Only the canvas app calls this' is a genuine scoping/exclusion signal that tells an agent this is not a general-purpose tool it should invoke on its own initiative. However, it gives no guidance on what the agent should do instead, nor any prerequisites or alternatives among the many sibling tools.

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

All Clypmint 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?