Skip to main content
Glama

analyze_trajectory

Checks recorded joint trajectories offline for jerk spikes, limit violations, slow profiles, and gaps, optionally using a URDF for joint limits. No running robot required.

Instructions

Offline quality check of a recorded joint trajectory (CSV, JSON or rosbag2) with trajlens: jerk spikes, limit violations, slow profiles, gaps. Needs no running robot. urdf adds joint limits.

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": {
      "path": "<path>"
    },
    "name": "analyze_trajectory"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
rateNo
urdfNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; it does disclose the operation is offline, requires no running robot, accepts three input formats, and names what it measures. It does not say whether the analysis is purely read-only, what the result looks like, or what happens on malformed recordings — gaps that matter for a tool with zero annotation coverage.

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?

Two dense sentences with zero filler, front-loading the core purpose and following with the constraint and the one parameter hint that matters. Every clause carries information.

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?

No output schema, no annotations, and 0% parameter coverage mean the description is the only documentation, and it leaves 'rate' undefined and says nothing about result contents. The purpose and format coverage are strong, so it is workable but incomplete for a three-parameter analysis tool.

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 should compensate, and it only partly does: 'urdf adds joint limits' gives real meaning to the urdf parameter (it enables limit-violation checks). The 'rate' parameter and the 'path' format expectations receive no explanation at all in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Offline quality check of a recorded joint trajectory') plus the concrete checks performed (jerk spikes, limit violations, slow profiles, gaps) and the accepted formats (CSV, JSON, rosbag2). The phrase 'Needs no running robot' cleanly separates it from the live-robot diagnose_* siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Offline quality check' and 'Needs no running robot' make the triggering context clear: post-hoc analysis of recorded data rather than live diagnosis. It does not, however, name an alternative tool or state exclusions explicitly, so the agent must infer that live-state siblings are inappropriate.

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