Skip to main content
Glama

get_joint_info

Retrieve actual joint ranges, counts, and actuator names from a pinned musculoskeletal engine model by model ID, optionally for a specific joint; ranges are not human norms.

Instructions

Compile pinned engine model for actual joint ranges, counts and actuator names. Ranges are not human norms.

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": {
      "model_id": "<model_id>"
    },
    "name": "get_joint_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
jointNo
model_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.1

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does disclose a meaningful semantic trait — that the ranges come from the pinned engine model rather than human norms — but says nothing about whether this is a pure read, what happens if the model is not pinned, whether an unpinned model errors, or what the cost of compiling is.

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?

Two short sentences with no filler, and the core purpose is front-loaded. The first sentence is densely packed with four concepts, which makes it slightly harder to parse, but nothing is wasted.

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?

The presence of an output schema means return values need not be described, and the "not human norms" caveat usefully frames interpretation. However, with 0% schema coverage the description leaves the optional `joint` filter undocumented and gives no conditions under which the tool should be preferred over its model-inspection siblings.

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% for two parameters, so the description must compensate and it largely does not. "pinned engine model" loosely maps to model_id, but the nullable `joint` parameter is never explained — notably whether omitting it (default null) returns every joint or behaves differently — which is the key invocation decision.

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?

"Compile pinned engine model for actual joint ranges, counts and actuator names" names a concrete resource (joint data of a pinned engine model) and enumerates the three things returned. It is distinguishable from describe_model and get_model_capabilities because it is explicitly about joint ranges/actuator names, though the verb "Compile" is unusual for what reads as a data retrieval tool.

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?

No guidance on when to call this versus get_model_capabilities or describe_model, and no statement of prerequisites beyond the required model_id. The only guidance-adjacent content is the interpretive caveat "Ranges are not human norms," which is about reading results, not about choosing the tool.

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