Skip to main content
Glama

list_scenarios

Discover validated scenario folders and isolate malformed or unsupported manifests with diagnostics, so you can identify runnable simulation scenarios before execution.

Instructions

Discover validated scenario folders; isolate malformed or unsupported manifests with diagnostics.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_scenarios"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it does disclose useful behavior beyond a plain listing: only validated folders are returned, while malformed/unsupported manifests are isolated and reported with diagnostics rather than failing the call. It does not state that the operation is read-only, whether scanning is recursive, or how permissions or missing roots are handled.

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 compact sentence with the primary outcome front-loaded and the diagnostic behavior second. The phrasing is dense jargon ("isolate malformed or unsupported manifests") but nothing is redundant or padded.

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

Completeness4/5

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

For a zero-parameter lister with an output schema, the description covers what is enumerated (validated folders) and how failures are treated (isolated with diagnostics), which is about as much as an agent needs. Only the scope of scanning is left unstated.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. No parameter claims are made that could conflict with the empty schema.

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?

"Discover validated scenario folders" names a concrete verb (discover) and resource (scenario folders), and the second clause adds the diagnostic side effect, which distinguishes it from the describe_* and run_* siblings. It stops short of explicitly contrasting itself with describe_scenario or list_models, so the differentiation is inferred rather than stated.

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 explicit when-to-use or when-not-to-use guidance and no alternative is named; the only implied usage is that it surfaces malformed or unsupported manifests with diagnostics. An agent must guess that this is the correct entry point before calling describe_scenario or run_scenario.

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