Skip to main content
Glama

scenario_describe

Read-onlyIdempotent

Describe the bound scenario's editable file globs, split sizes, budgets, scorer version, and readiness before editing; use it first to see what can be changed and how large each split is. Read-only.

Instructions

Describe the bound scenario: epoch id, editable file globs, frozen scorer version, task counts per split, primer, budgets, replay support and readiness flags. Call it first to learn what may be edited and how large each split is; use version_current for the current version id and ledger_history for lineage. Read-only; never reveals confirmation or final task ids. Returns one JSON object.

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": {
      "config": "<config>"
    },
    "name": "scenario_describe"
  }
}

Input Schema

NameRequiredDescriptionDefault
configYesPath of the scenario YAML file on the server host, absolute or relative to the server's working directory, for example `scenario.yaml`. It selects the workspace; a server started with --config rejects any other path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.9
    • addedInput schema / properties / config / description
      Added value: +"Path of the scenario YAML file on the server host, absolute or relative to the server's working directory, for example `scenario.yaml`. It selects the workspace; a server started with --config rejects any other path."
  2. First observedv0.1.7

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered structurally. The description still adds non-obvious behavior: it is read-only, deliberately withholds confirmation/final task ids, and returns exactly one JSON object — disclosure an agent cannot get from annotations. It does not describe error behavior when the config path is rejected, keeping it short of a 5.

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 sentences, front-loaded with what is returned before routing advice. The middle enumeration is dense but every item is a distinct returned field; no filler text. Slightly heavy comma-list keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description enumerates the return payload, states the return shape (one JSON object), defines the read-only and withholding behavior, and positions the tool first in the workflow. Nothing an agent needs in order to call this correctly is missing.

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

Parameters3/5

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

There is a single parameter with 100% schema description coverage, so the schema already explains the config path, its absoluteness/relativity and the --config binding restriction. The description adds only the framing that the scenario is "bound" to that config; it does not elaborate further, so baseline 3 applies.

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

Purpose5/5

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

Specific verb+resource ("Describe the bound scenario") followed by an enumeration of exactly what is returned: epoch id, editable globs, frozen scorer version, split task counts, primer, budgets, replay support, readiness flags. It is clearly distinguishable from version_current and ledger_history, which it names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Call it first to learn what may be edited and how large each split is" gives explicit ordering guidance, and it routes two adjacent needs to named alternatives (version_current for version id, ledger_history for lineage). Both when-to-use and when-to-use-something-else are covered.

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