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

mcp-for-cascadeur

by Rickcy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

semantic_pose_read_sequence

Read-only

Reads semantic body targets for specified roles at bounded existing frames without moving the playhead, so you can inspect poses at exact animation times.

Instructions

Read semantic body targets at bounded existing frames without moving the playhead.

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": {
      "frames": "<frames>"
    },
    "name": "semantic_pose_read_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
rolesNo
framesYes
characterNo
include_joint_stateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds a genuinely new behavioral fact — that the playhead is not moved — which is app-state context annotations cannot express. It stops short of saying whether nonexistent frames error or are skipped.

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?

A single front-loaded sentence with the action first and the constraints after; nothing is wasted. It is efficient but so compressed that the frame-bounds rule stays ambiguous.

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?

With no output schema and no parameter descriptions, the description should explain the per-frame/per-role structure of the returned pose targets and the meaning of the optional parameters. It covers none of that, leaving an agent to guess at both inputs and results for a 4-parameter read.

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 description coverage is 0% across four parameters, so the description carries the full burden. It gestures at 'frames' and 'semantic body targets' (roles), but says nothing about the allowed role enum values, what 'character' selects, or what 'include_joint_state' changes in the result.

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 and resource ('Read semantic body targets') plus a scope qualifier ('at bounded existing frames'), which implicitly separates it from the single-frame sibling semantic_pose_read. It never names that sibling explicitly, so differentiation is inferential rather than stated.

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?

'Bounded existing frames' implies frames must already exist and be inside the sequence range, which hints at when the tool applies. However, there is no explicit routing versus semantic_pose_read, pose_read_sequence, or rig_pose_read, and no statement of what to do for out-of-range frames.

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