Skip to main content
Glama

test_get_results

Read-only

Retrieve a scenario run by ID to inspect its state, step counts, failures, cleanup errors, and error log references for debugging and validation.

Instructions

Get a scenario run by ID: state, step counts, failures, cleanup errors and error log references

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": {
      "id": "<id>"
    },
    "name": "test_get_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful disclosure of what the result contains (failures, cleanup errors, error log references), which is genuinely behavioral value. It does not say what happens when the ID is unknown or invalid, or whether state values are enumerated.

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 line with no filler, and the most decision-relevant part (what operation, on what resource) comes first. It is a fragment rather than a full sentence, but nothing is wasted and the field list is dense with information.

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?

No output schema exists, so the enumeration of returned fields carries real weight and is present. For a one-parameter read tool whose annotations cover safety, this is close to complete; only error behavior on a bad/missing ID is left unstated.

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 one parameter at 0% schema description coverage; the schema only encodes a UUID pattern. The phrase 'by ID' tells the agent the ID identifies a scenario run, which is minimal but real compensation. It does not clarify where such an ID comes from (presumably the execute/create tools) or how malformed IDs are handled.

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 and resource ('Get a scenario run by ID') and then enumerates the returned content (state, step counts, failures, cleanup errors, error log references). This makes it clearly a single-run retrieval tool, distinguishable from execution/cleanup siblings, though it never names a sibling explicitly.

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: 'by ID' signals this is the read-side counterpart to running a scenario, but there is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as log or diagnostics tools. An agent can infer the context but must do the work itself.

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