Skip to main content
Glama

review_motion_contacts

Read-only

Check phase-specific contact rules across an animation and restore the starting frame, with optional sampled views, prior evidence reuse, and isolated background review.

Instructions

Check phase-specific contact rules across an animation and restore the starting frame.

Supply a version 1 profile with named surfaces and rule intervals. Optional extra_frames replay sample times from a previous review. Request two views for matched evidence at representative samples. Use match_evidence to reuse prior frames and framing. Use blend_file for an isolated background review.

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": "review_motion_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewsNo
profileYes
timeoutNo
blend_fileNo
extra_framesNo
evidence_ruleNo
match_evidenceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, and the description is consistent with that framing. It adds useful behavioral detail beyond the annotations: the starting frame is restored afterward, the profile must be version 1 with named surfaces and rule intervals, and two views should be requested for matched evidence. It does not explain the timeout/run-length behavior, what happens on rule failure, or how the restore interacts with the user's current frame.

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?

Six short sentences, front-loaded with purpose and then parameter guidance, with no filler. The telegraphic, fragmentary style ('Request two views for matched evidence at representative samples') is dense but never padded.

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 values need not be described. However, for a 7-parameter tool with a free-form nested profile object and zero schema documentation, the description omits evidence_rule and timeout and only sketches the profile's internal structure, leaving real gaps before an agent can call it confidently.

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

Parameters4/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 covers five of the seven parameters with meaningful semantics: profile (version 1, named surfaces, rule intervals), extra_frames (replays sample times from a prior review), views (request two for matched evidence), match_evidence (reuse prior frames and framing), and blend_file (isolated background review). It leaves evidence_rule and timeout entirely unexplained, which keeps it from a 5.

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 first sentence gives a concrete verb and resource ('Check phase-specific contact rules across an animation') plus a side effect ('restore the starting frame'), which is enough to tell this apart from evaluation-only or inspection tools. It never names a sibling (e.g. compare_motion_reviews or inspect_clothing_fit), so the boundary with adjacent review tools stays implicit.

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?

The description tells the agent how to drive individual parameters ('Use match_evidence to reuse prior frames and framing', 'Use blend_file for an isolated background review'), which is real routing guidance. It does not state when this tool should be chosen over compare_motion_reviews or inspect_clothing_fit, nor any when-not conditions or prerequisites such as a loaded scene.

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