Skip to main content
Glama

get_robot_info

Read-only

Read a robot's structure and joint states before driving it: link and DOF counts, joint names, types, limits, drives, plus current positions and velocities from USD or physics.

Instructions

Read a robot: from USD, at any time, whether it is an articulation, its link and DOF counts, and each joint's name, type, limits and drive; from physics, while the simulation plays or is paused, each joint's position and velocity.

Use it before driving a robot, and to see where its joints are now. Limits are as USD holds them: degrees for revolute joints, stage units for prismatic ones. Joint states are in radians for revolute joints and stage units for prismatic ones, velocities per second; set_joint_targets takes degrees. The Joints list comes in the order a list of set_joint_targets follows, fixed joints included, and the DOF count leaves fixed joints out; the joint states come in physics' own order of degrees of freedom. Stopped, or in a Kit app without Isaac Sim, the answer gives the structure and a line saying why there are no joint states. prim_path is the robot's root: the joint states are the first articulation's at or under it. An answer too long to give inline keeps the counts, and the joint states where they fit, and writes the Joints list to a file, its path in the answer.

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": {
      "prim_path": "<prim_path>"
    },
    "name": "get_robot_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
prim_pathYesThe robot's root prim, e.g. "/World/G1"

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint=false, so the description carries real weight and delivers: unit conventions (degrees vs radians vs stage units), that limits reflect USD values rather than live values, ordering rules for the Joints list vs the DOF-ordered joint states, and the truncation-to-file fallback with the path echoed back. It also discloses the degraded path when the sim is stopped or Isaac Sim is absent.

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?

Content is front-loaded with the tool's purpose and every clause carries distinct information about units, ordering, or fallbacks. The long semicolon-chained sentences are dense and could be split into a short list of invariants for faster scanning.

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

Completeness5/5

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

Despite an output schema, the description supplements it with the ordering and truncation semantics an agent needs to interpret results correctly, plus the no-sim and too-long response cases. Nothing material for correct invocation or interpretation is missing.

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 100% and the single parameter is documented as the root prim, so the baseline is 3; the description goes further by explaining that joint states are taken from the first articulation at or under that path, which resolves genuine ambiguity about sub-articulation prims.

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 opening sentence names a specific verb and resource (read a robot) and enumerates exactly what is returned: articulation status, link/DOF counts, per-joint name/type/limits/drive, and live joint positions/velocities. It clearly distinguishes robot articulation reads from generic prim reads, though it never names inspect_prim or get_prim_properties as the narrower/wider alternatives an agent might otherwise pick.

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?

"Use it before driving a robot, and to see where its joints are now" gives an explicit use context, and the repeated contrast with set_joint_targets (radians/degrees) steers the agent to the right tool pairing. There is no explicit when-not guidance, e.g. that non-robot prims should go to get_prim_properties.

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