Skip to main content
Glama
Sign In
mcp-for-cascadeur

mcp-for-cascadeur

by Rickcy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

playback_start

Destructive

Starts bounded native playback over a specified frame range after verifying the playhead is stationary, observes real frame changes, and auto-stops; avoids scripting per-frame movement.

Instructions

Start bounded native playback after checking a stationary playhead; observe real frame changes and auto-stop. Never scripts per-frame movement.

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": {
      "first": "<first>",
      "last": "<last>"
    },
    "name": "playback_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
lastYes
firstYes
timeoutNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only supply the generic safety profile (destructiveHint=true, openWorldHint=false). The description adds genuinely non-obvious behavior: playback is bounded, it auto-stops, it is native rather than scripted, and it must begin from a stationary playhead. It does not say what state playback leaves behind or how failure/timeout surfaces.

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 dense sentences with the action front-loaded and the constraint trailing. Nothing is redundant, though the phrase "Never scripts per-frame movement" is terse enough to be slightly ambiguous about whether it describes this tool's own behavior or warns against a workaround.

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?

With no output schema and three fully undocumented parameters, the description leaves the caller guessing about the numeric arguments and about how to observe results. The behavioral story (bounded, auto-stop, real frame changes) is adequate, but for a state-changing playback tool the parameter and completion semantics are thin.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the full burden, and it does not mention first, last, or timeout at all. An agent cannot tell from the text whether first/last are frame numbers, a count, or an inclusive range, nor what the timeout governs. Only the vague word "bounded" hints at the range.

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 names a specific verb and resource: "Start bounded native playback." The word "bounded" plus "auto-stop" distinguishes it from an unbounded play loop, and the sibling set (playback_stop, playback_status) makes the intended role clear. It stops short of explicitly naming those siblings.

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?

A precondition is stated ("after checking a stationary playhead") and a prohibition is given ("Never scripts per-frame movement"), which is real guidance. However, it never names playback_stop or playback_status as the follow-up alternatives, nor does it say what to do when the playhead is not stationary.

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

Deploy Server

Other Tools