Skip to main content
Glama

compare_motion_reviews

Read-only

Compare two motion review reports from the same profile to verify matching rule and frame samples, replay missing times with extra_frames, and drop unneeded evidence.

Instructions

Compare two motion review data reports from the same profile.

The delivered comparison counts only matching rule and frame samples as verified. Replay missing sample times with extra_frames. Drop evidence from the input if needed.

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": {
      "before": "<before>",
      "after": "<after>"
    },
    "name": "compare_motion_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterYes
beforeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine behavioral semantics ('counts only matching rule and frame samples as verified'), which tells the agent how results are judged, but the line 'Drop evidence from the input if needed' is ambiguous about who drops evidence and borders on implying input mutation despite readOnlyHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short and front-loaded with the core purpose, with no filler sentences. However, the two trailing guidance sentences are cryptic enough that they cost clarity without delivering actionable instruction, so brevity does not translate into efficiency here.

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?

An output schema exists, so return values need not be explained, but the inputs are untyped nested objects at 0% coverage and the description does not describe their expected shape. For a comparison tool whose correctness depends on the two reports being compatible, the definition leaves too much for the agent to infer.

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 both parameters are free-form objects with additionalProperties, so the schema provides essentially no meaning. The description only gestures at relevant fields ('extra_frames', 'evidence') without explaining the structure of before/after reports, leaving the agent unable to construct valid input confidently.

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 concrete verb and resource: 'Compare two motion review data reports', plus a scope constraint ('from the same profile'). It does not differentiate from nearby tools like jump_to_motion_witness or review_motion_contacts, and it never says what a 'motion review data report' is, so the purpose is clear at a high level but underspecified in substance.

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?

There is no explicit when-to-use or when-not-to-use guidance and no alternative tool is named. The only operational hints are 'Replay missing sample times with extra_frames' and 'Drop evidence from the input if needed', which describe handling of edge cases rather than when an agent should pick this tool.

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