Skip to main content
Glama

get_result

Retrieve persisted musculoskeletal simulation results by run ID, including run status, computed metrics with units, evidence, limitations, and artifact IDs.

Instructions

Retrieve persisted run status, computed metrics with units, evidence, limitations and artifact IDs.

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": {
      "run_id": "<run_id>"
    },
    "name": "get_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.1

TDQS

B3.1/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 and falls short. It does not say what happens if the run_id is unknown or still running, whether the call blocks, whether results are cached, or what permissions are needed. "Persisted" is the only behavioral hint offered.

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?

One sentence, front-loaded with the verb, with no filler. Nothing is redundant or padded, and the enumeration is scannable.

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?

An output schema exists, so the description arguably needn't enumerate return fields — yet that listing is most of its content, while genuinely missing context (run_id provenance, behavior for incomplete or nonexistent runs, relationship to run_scenario) goes uncovered. For a simple one-parameter read tool with a rich output schema it is adequate but lopsided.

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 parameter run_id has 0% schema description coverage, and the description does not compensate at all — it never explains where run_id comes from, its format, or that it is required. The parameter is only implicitly acknowledged via "run".

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?

Specific verb ("Retrieve") plus a concrete resource (persisted run status, computed metrics, evidence, limitations, artifact IDs). An agent can tell it apart from get_artifact or render_result by the payload described. It stops short of naming siblings, so no explicit differentiation.

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?

No explicit when-to-use or when-not-to-use statement. The word "persisted" implies this is for runs already recorded rather than triggering work, and the enumerated contents implicitly tell an agent to come here when it needs metrics/evidence. Alternatives and preconditions are never stated.

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