Skip to main content
Glama

describe_model

Retrieves provenance and metadata—source, license, version, scope, units, and limitations—for a specified musculoskeletal model ID, helping you assess suitability before simulation.

Instructions

Model source, license, version, scope, units, limitations. get_joint_info compiles actual geometry.

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": "describe_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It names the metadata categories returned, implying a read-only describe operation, but does not state permissions, side effects, error behavior, or confirm read-only safety.

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 short, front-loaded fragments with no filler; the field list comes first and the sibling contrast follows immediately. It is telegraphic but highly efficient.

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?

For a simple one-parameter read tool with an output schema, the description names the returned metadata categories and the geometry alternative. It leaves model_id sourcing/format and read-only assurance unaddressed, which are meaningful gaps given the absence of annotations.

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?

The single required model_id parameter has 0% schema description coverage and is not mentioned in the description. The agent can infer that it identifies the model from context, but the description adds no format, source, or usage guidance for it.

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?

It enumerates the metadata returned (source, license, version, scope, units, limitations) and distinguishes this tool from get_joint_info by contrast. The purpose is clear, though the description uses a telegraphic noun phrase rather than an explicit verb.

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 explicitly routes geometry requests to get_joint_info, which implies this tool is for metadata inspection instead. It does not spell out formal when-not conditions or prerequisites, but the intended context is clear.

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