Skip to main content
Glama

get_model_capabilities

Check which outputs and quantities a musculoskeletal model supports before running simulations; unsupported organs, safety advice, and invented computations are rejected.

Instructions

Return supported outputs; reject organs, safety advice and unsupported computations without invented values.

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_model_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_idYes
quantityNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.1

TDQS

C2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions rejecting certain requests and avoiding invented values, but does not describe read-only behavior, error handling, authorization, or other operational traits beyond that vague guardrail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence and is front-loaded with the intended action, but the second clause is confusing and of questionable relevance. It is concise but not efficiently informative.

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?

An output schema exists, so return values need not be explained. However, for a tool with two undocumented parameters and no annotations, the description is too incomplete: it omits what the model_id identifies, what quantity means, and when the tool should be used.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not mention either parameter. The required model_id and optional quantity are left entirely undocumented in the description, so it adds no semantic meaning beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says "Return supported outputs," which is vague and does not clearly state that it retrieves model capabilities for a given model. The added clause about rejecting organs and safety advice is confusing and does not clarify the tool's actual purpose relative to siblings such as describe_model or list_models.

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?

There is no guidance on when to use this tool versus alternatives like describe_model or list_models. The rejection language implies content boundaries but does not help an agent choose this tool for a specific task.

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