Skip to main content
Glama

list_runs

Retrieve recent run IDs and verdicts from the store, newest first, with a configurable limit for reviewing or comparing experiment results.

Instructions

List recent IDs and verdicts in this store, most recent first (limit 1..200).

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_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the full burden. It does disclose ordering (most recent first), the valid limit range (1..200), and that results are limited to IDs and verdicts rather than full run data. It does not say what happens beyond 200 results, whether there is pagination, or what a 'verdict' value can be.

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?

A single front-loaded sentence with the ordering constraint early and the range in a compact parenthetical. No redundant or filler wording.

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 simple one-parameter list tool with no output schema, the description covers order, return content, and the limit range. The remaining gaps (behavior past 200 results, enumerable verdict values) are minor but real for an agent planning retrieval.

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 only parameter, limit, has 0% schema coverage (schema gives just type integer and default 20), so the description's 'limit 1..200' supplies the missing valid range. It could additionally state what the limit counts or how it interacts with 'recent', but the added constraint is genuinely useful.

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 uses a specific verb plus resource ('List recent IDs and verdicts in this store') and states the return shape (IDs and verdicts, not full records) and ordering. It is clearly distinguishable from get_run or review by its summary-list nature, though it does not name 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: 'recent' and 'list' suggest using this as a discovery/overview step before fetching details with get_run or comparing runs. No explicit when-to-use, when-not-to-use, or alternative is named, and nothing tells the agent whether this is the right entry point versus describe or parameter_history.

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