Skip to main content
Glama

run_scenario

Run bounded musculoskeletal simulation scenarios with validated inputs and optional idempotency-key reuse to return numeric results and model evidence.

Instructions

Execute a bounded real engine operation. Unknown parameters rejected. Optional key reuses the same run.

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": {
      "scenario_id": "<scenario_id>"
    },
    "name": "run_scenario"
  }
}

Input Schema

NameRequiredDescriptionDefault
parametersNo
scenario_idYes
idempotency_keyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.1

TDQS

C2.8/5.0
Behavior3/5

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

With no annotations, the description still contributes concrete behavior: strict rejection of unknown parameters and idempotency semantics ('Optional key reuses the same run'). It omits the important traits though — whether the run has side effects, how long it takes, and whether results arrive later via the sibling get_result, which the presence of that sibling strongly suggests.

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?

Three short sentences, front-loaded with the action, then validation, then the key. Nothing is padded, though the terseness edges into under-specification rather than economy.

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 output schema covers return values and the description covers validation and idempotency, but for an execution tool with no annotations an agent still lacks the run lifecycle (sync vs async, where to fetch results) and side-effect profile.

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 coverage is 0%, so the description must carry all three parameters. It explains idempotency_key well ('reuses the same run') and hints that the parameters object is validated against a known set ('Unknown parameters rejected'), but scenario_id gets no meaning at all and the accepted parameter keys/format remain undocumented.

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

Purpose3/5

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

The verb 'Execute' is clear, but the resource is described only as 'a bounded real engine operation' — the word 'scenario' never appears in the description despite being the tool's subject and the name of a sibling family (list_scenarios, describe_scenario). An agent can guess this runs a scenario_id, but not from the text alone.

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 call this versus describe_scenario or list_scenarios, and no prerequisites stated (e.g. must the scenario be described or have sources attached first). Execution-vs-inspection is only implied by the word 'Execute'.

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