Clypmint

Measure a move

measure_motion

Read-onlyIdempotent

Times a move frame by frame (a clip on the video, or a graphic) and names its ease, with a graph. 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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "measure_motion"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	Just after it settles; at most from + 4.
`from`	Yes	Just before the move.
`every`	No	Seconds per frame; 1/30.
`region`	No	[x, y, width, height] fractions: one thing among several.
`against`	No	Compare with one end only.
`video_id`	No	Video; the open one if left out.
`output_id`	No	Output id.
`base_version`	No	Version id.

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

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuine extra context in 'Cost: Free' and in promising a graph as part of the result, but it does not disclose constraints such as the short sampling window (at most from + 4) or that it compares against both ends by default unless 'against' is set.

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?

Two short, front-loaded sentences with no filler; the verb and result come first and the cost note trails. The nested parenthetical in the first sentence is slightly awkward but costs little.

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

Completeness3/5

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

An output schema exists, so return-value explanation is not required, and annotations carry the safety profile. However, for an eight-parameter measurement tool whose required fields ('from'/'to') are only described in the schema as 'just before the move' and 'just after it settles,' the description does not establish the coordinate space or what a caller must know before sampling.

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 every one of the eight parameters is already documented, which sets the baseline at 3. The description only loosely gestures at 'every' (frame by frame) and 'against' (naming its ease by comparison) without adding format, units, or default semantics beyond the schema.

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?

The description gives a concrete verb and object: it 'times a move frame by frame' and 'names its ease, with a graph,' which tells an agent exactly what comes back (a timing measurement plus an easing classification). The parenthetical scope note ('a clip on the video, or a graphic') clarifies the resource, but the phrasing is loose enough that the exact unit of 'a move' requires the schema to pin down.

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?

There is no statement of when this tool should be used versus alternatives in the sibling list (get_timeline, get_screenshot, check_video), nor any prerequisites or exclusions. The only guidance is commercial ('Cost: Free'), which helps an agent weigh the call but says nothing about selection.

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?