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

mcp-for-cascadeur

by Rickcy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pose_read_euler

Read-only

Read native Cascadeur rig object positions, quaternions, and Euler angles in radians, with optional frame and local/global space selection.

Instructions

Read actual native positions, quaternions and Euler angles in radians.

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": {
      "objects": "<objects>"
    },
    "name": "pose_read_euler"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameNo
spaceNoglobal
objectsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/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 safety behavior is covered. The description adds output data types and radians, but does not explain frame semantics, object scope, or return structure; with no output schema, more behavioral detail would help.

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 filler or repetition. It efficiently states the core operation and returned data.

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 three-parameter read tool with no output schema and 0% schema description coverage, the description is too thin. It covers high-level outputs but omits parameter behavior, object scope, and return shape needed for correct invocation.

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%, and the description explains none of the three parameters: frame, space, or objects. The mention of radians clarifies output units rather than parameter meaning, leaving the parameters undocumented.

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 read operation and the data returned: native positions, quaternions, and Euler angles in radians. It does not distinguish this tool from sibling pose-reading tools such as pose_read, rig_pose_read, semantic_pose_read, or pose_read_sequence.

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?

Provides no explicit guidance on when to use this tool versus sibling pose-read tools, nor any exclusions or prerequisites. In a sibling-heavy context, the missing routing cues are significant.

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