Skip to main content
Glama

inspect_rig

Read-only

Inspect resolved bone axes, controls, authored weights, and sampled motion with a v1 profile, capture front/side evidence at a frame, and link a motion review report for geometry findings.

Instructions

Inspect resolved bone axes, controls, authored weights and sampled motion using a version 1 profile.

Request front and side evidence at a sampled frame. Link an existing motion review report from the same scene for attached geometry findings. The operation restores the original frame.

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": {
      "profile": "<profile>"
    },
    "name": "inspect_rig"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewsNo
framesNo
profileYes
timeoutNo
blend_fileNo
contact_reportNo
evidence_frameNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, so the safety profile is largely covered. The description adds genuinely new context beyond that: it changes view/frame state and then 'restores the original frame', and it links in an external motion review report — important for an agent reasoning about side effects and evidence provenance.

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?

Four short sentences, front-loaded with the object of inspection before the supporting scenarios, and the state-restoration note earns its place. Some phrasing ('using a version 1 profile', 'attached geometry findings') is opaque enough to feel like compressed internal jargon rather than efficient specificity.

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 has 7 parameters, nested open-ended objects, and a required 'profile' with no documented shape, yet the description never explains what that profile contains or what values it accepts. The output schema excuses it from covering return values, but the input side — especially the required parameter and timeout/blend_file — remains materially under-specified.

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 0%, so the description must compensate and it only partially does. It hints at 'views' (front and side evidence), 'frames'/'evidence_frame' (sampled frame), 'contact_report' (linked motion review report), and gives one detail on 'profile' (version 1) — but the required 'profile' object, 'timeout', and 'blend_file' get no explanation, and the mappings are implicit rather than explicit.

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?

Uses a specific verb (Inspect) tied to concrete resources — resolved bone axes, controls, authored weights, and sampled motion — which clearly places it apart from siblings like inspect_clothing_fit or inspect_spatial_pairs by domain. It never explicitly names a sibling or contrasting alternative, so it stops short of full differentiation.

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?

Implied usage is present: 'Request front and side evidence at a sampled frame' and 'Link an existing motion review report from the same scene for attached geometry findings' describe two scenarios. However there is no explicit when-not-to-use and no named alternative tool for overlapping tasks (e.g. compare_motion_reviews), leaving routing to inference.

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