Skip to main content
Glama

list_runs

Lists cached S3 pipeline runs with run ID, paper count, best threshold, and label status so you can inspect prior analyses before continuing.

Instructions

List saved S3 runs (run_id, number of papers, best threshold, labels saved?).

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

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.2

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. The word "List" plus "saved" implies a non-mutating enumeration of persisted results, which is useful, but ordering, pagination, and the empty-result case are all unstated, and the terse "labels saved?" leaves the semantics of that field ambiguous.

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 sentence, front-loaded with the verb and resource, with no filler. The trailing parenthetical is efficient but slightly cryptic, particularly "labels saved?" whose question mark and capitalization are unexplained.

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?

With no parameters and an output schema present, the description need not describe return values, and it correctly stays short. What is missing is small but real: no hint about result ordering or volume, and no link to the sibling that creates these runs, which would help an agent decide between listing and running.

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 beyond the input schema. Baseline 4 applies; the parenthetical field list is about outputs, not inputs.

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?

"List saved S3 runs" gives a specific verb and resource, and the parenthetical names the fields each run carries (run_id, paper count, best threshold, labels). An agent can distinguish it from siblings like run_s3_analysis or get_threshold_scan, though the description never explicitly ties a run to the analysis tool that produces it.

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: "saved" hints this is for enumerating prior results rather than launching new work, which weakly routes against run_s3_analysis. There is no explicit when-to-use, no statement of prerequisites such as whether runs must have been saved first, and no named alternative.

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