Skip to main content
Glama

check_reach

Checks whether a UR3 or UR5e arm can reach a tool-down pose at given x, y, z coordinates offline, returning reachability, IK error, manipulability, and joint-limit margin.

Instructions

Can a UR arm (ur3 or ur5e) reach a tool-down pose at x, y, z metres in the base frame? Returns reachable, the IK error, manipulability and joint-limit margin. Offline, no robot needed (MuJoCo IK via reachlens).

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": {
      "x": "<x>",
      "y": "<y>",
      "z": "<z>"
    },
    "name": "check_reach"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
zYes
armNour3
tool_lengthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the return surface (reachable, IK error, manipulability, joint-limit margin), the offline/simulated execution model, and the solver used. It omits failure behavior (e.g. what happens for an unsupported arm name or unreachable geometry) and any performance/cost characteristics.

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 sentences, front-loaded with the question the tool answers, then the return values, then the execution environment. No filler or restatement of the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter, annotation-free tool with no output schema, the description adequately covers what the result contains, the units/frame, and the offline execution mode. The only meaningful gap is the unexplained tool_length parameter.

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 coverage is 0%, so the description must compensate, and it does add real meaning for x, y, z (metres, base frame) and for arm (valid values ur3 or ur5e, effectively an enum). However, the fifth parameter tool_length is never mentioned, leaving an undocumented default of 0 that materially affects the reach result.

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 description states a concrete verb and resource ('reach a tool-down pose at x, y, z metres in the base frame') for a specific hardware family (ur3 or ur5e) and names the metrics returned. It is clearly distinguishable from the sibling diagnostic/analysis tools, though it does not explicitly contrast itself with any of them.

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?

It frames the exact question the tool answers ('Can a UR arm reach...') and adds a selection-relevant condition: 'Offline, no robot needed (MuJoCo IK via reachlens)', telling the agent this can be used without a live robot. It stops short of stating when NOT to use it or naming an alternative.

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