Skip to main content
Glama

run_results

Read-onlyIdempotent

List committed task results for one experiment arm—task, group, repeat, outcome, reason, cost, time, output and trace path—to inspect raw evidence; read-only and partial while running.

Instructions

List one arm's committed task results: task_id, group, repeat, outcome, reason, cost, seconds, output and archived trace path. Use it for raw evidence; use failure_cards for failures only and compare_paired for parent-versus-child deltas. Read-only; partial while the arm is running. Returns an array in stable order.

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>",
      "run_id": "<run_id>"
    },
    "name": "run_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum items to return, at least 1. Omit to return all remaining items.
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.
offsetNoZero-based index of the first item to return. Default 0.
run_idYesRun id of a diagnosis or selection arm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields 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."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum items to return, at least 1. Omit to return all remaining items."
    • addedInput schema / properties / offset / default
      Added value: +0
    • addedInput schema / properties / offset / description
      Added value: +"Zero-based index of the first item to return. Default 0."
    • addedInput schema / properties / run_id / description
      Added value: +"Run id of a diagnosis or selection arm."
  2. First observedv0.1.7

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description still contributes real behavioral context beyond them: results are "partial while the arm is running" and the array is returned in "stable order," both of which matter for an agent deciding whether to trust an incomplete snapshot. It stops short of describing page-size or continuation behavior, which the schema handles.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences, each doing distinct work: what is returned, how it differs from siblings, and how it behaves. The routing sentence precedes the behavioral caveat, so the highest-value disambiguation is front-loaded with no filler.

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 field enumeration compensates well for the absent output schema, and the partial/stable-order notes cover runtime behavior. What is left implicit is how pagination interacts with the running state, for example whether an offset stays valid once new results are committed mid-run, which an agent calling this repeatedly would need to know.

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?

Schema description coverage is 100%, so the schema already explains config, run_id, limit and offset, and the description adds nothing parameter-specific. The enumerated return fields carry output meaning that the missing output schema would otherwise leave blank, which lifts it slightly above the baseline.

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?

States a specific verb and resource with scope: "List one arm's committed task results," and enumerates exactly which fields come back (task_id, group, repeat, outcome, reason, cost, seconds, output, archived trace path). That detail separates it immediately from siblings like run_status or ledger_history.

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?

Explicitly routes the agent: "Use it for raw evidence; use failure_cards for failures only and compare_paired for parent-versus-child deltas." Both the when-to-use case and the two named alternatives with their distinguishing conditions are given, leaving nothing to inference.

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