Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

robot_solve_ik

Read-only

Finds a URDF inverse-kinematics candidate in the base frame for a target position and optional orientation; it does not check collisions.

Instructions

Find a URDF IK candidate in the base frame; does not check collisions.

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": {
      "urdf_path": "<urdf_path>",
      "base_link": "<base_link>",
      "tool_link": "<tool_link>",
      "joint_names": "<joint_names>",
      "target_position": "<target_position>"
    },
    "name": "robot_solve_ik"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNo
base_linkYes
tool_linkYes
urdf_pathYes
joint_namesYes
target_positionYes
target_orientation_wxyzNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 the safety profile is covered. The description adds genuinely useful behavior: results are collision-unchecked and the return is a 'candidate' (implying non-uniqueness and possible failure), but it says nothing about whether one solution or many are returned, how seed influences the solution branch, or what happens on an unreachable target.

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?

A single compact sentence with the key caveat attached via a semicolon — zero padding and front-loaded with the action. Nothing here could be cut without losing information.

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?

For a 7-parameter, 5-required kinematics tool with no output schema and no annotation-level detail on returns, the description is too thin. An agent cannot tell the return shape (single pose plus joint values?), the units and orientation convention for the target, or what a failed solve looks like, all of which the description must supply since no output schema exists.

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% across 7 parameters, so the description carries the full burden and largely fails it: it never mentions seed, target_orientation_wxyz optionality, units for target_position, or what joint_names must contain. 'In the base frame' is the only semantic hint, loosely tying base_link to the output frame, which is insufficient for five required parameters.

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 specific verb and resource ('Find a URDF IK candidate') plus a frame qualifier ('in the base frame'), which tells an agent this is an inverse-kinematics solve returning a candidate rather than a plan or a trajectory. It does not name or differentiate itself against any of the planning/verification siblings, so it stops short of a 5.

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?

'does not check collisions' implicitly signals that a collision check must happen elsewhere (e.g. run_contacts/run_verify), which is real routing guidance, though it is phrased as a caveat rather than an explicit when-to-use rule. There is no statement of prerequisites, no mention of when to prefer a full planner like robot_plan_pick_cycle, and no note on what to do when the solve fails.

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