Skip to main content
Glama

describe_scenario

Retrieve a simulation scenario's version, method, required capabilities, scope, backend, and default parameters to inspect setup before running it.

Instructions

Return scenario version, method, required capabilities, scope, backend and default parameters.

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

Input Schema

NameRequiredDescriptionDefault
scenario_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. "Return" implies a non-mutating read, and the enumerated field list tells the agent what information is available, which is useful context. However, it says nothing about behavior on an unknown scenario_id, permissions/capability requirements to describe a scenario, or cost of the call.

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?

A single front-loaded sentence with no filler; every listed field carries information about what the call yields. It reads as a bare comma-separated inventory rather than structured prose, which slightly reduces scannability but is otherwise 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?

Return values are covered by the existing output schema, so enumerating them is supplementary rather than essential, and the single-parameter surface is simple. The missing piece is how to source the required scenario_id and what happens on a miss, which matters for correct invocation but is left to inference.

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 the single required parameter scenario_id, and the description adds nothing about its format, source, or expected values. An agent must guess whether this is a name, an ID from list_scenarios, or a version-qualified reference. With one undocumented parameter, the description should have compensated but does not.

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?

The description gives a specific verb ("Return") plus the resource (scenario) and enumerates the metadata fields returned: version, method, required capabilities, scope, backend, default parameters. That distinguishes it from siblings like list_scenarios or run_scenario by making clear it is a metadata read for one scenario. It stops short of explicitly naming a sibling alternative, so it falls just below the top mark.

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?

Usage is only implied: the required scenario_id signals that this operates on one already-known scenario, and the field list hints at pre-flight inspection before run_scenario. There is no explicit when-to-use, no guidance on how to obtain a scenario_id (e.g., via list_scenarios), and no stated exclusions.

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