Skip to main content
Glama

List data runs

list_data_runs
Read-only

List backup, restore and clone runs newest first (the twin of ankra runs list --kind backup). Use it to answer what a backup did, and when one failed. Read-only. Only offered when backups are enabled for the organisation.

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

Input Schema

NameRequiredDescriptionDefault
kindNoRestrict to one kind of data movement.
limitNoRows to return, 1 to 100. Defaults to 20.
statusNoRestrict to one run status, e.g. failed, running, succeeded, cancelled.
batch_idNoRestrict to one fan-out batch.
cluster_idNoUUID of the cluster. Alternative to cluster_name.
stack_nameNoRestrict to runs touching this stack.
cluster_nameNoExact name of the cluster. Optional when a cluster is already selected in the conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so repeating "Read-only" adds nothing; however the description contributes genuinely new behavioral facts: default newest-first ordering and the availability constraint tied to organisation backup enablement. Pagination behavior beyond the limit parameter and whether filters combine are left unstated.

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?

Three short sentences, front-loaded with the resource and ordering, then the use case, then the precondition. The CLI twin parenthetical ("the twin of `ankra runs list --kind backup`") is the one line that does not clearly earn its place for an agent that has no shell.

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 filtered read-only list tool with no output schema, the description covers purpose, ordering, use case, and availability, which is close to sufficient. It does not say whether the limit page is the whole result set or how many rows exist, which an agent would want before paginating.

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?

Schema description coverage is 100%, so every one of the seven optional filters is already documented in the schema. The description only echoes the kind enum ("backup, restore and clone") and adds no guidance on combining filters or on cluster_id vs cluster_name precedence, so the baseline 3 applies.

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?

States a specific verb and resource ("List backup, restore and clone runs") plus a scope detail ("newest first"), which is enough for an agent to know exactly what comes back. It does not name the sibling that returns a single run (get_data_run) or the restore-point listers, so differentiation is implied rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use it to answer what a backup did, and when one failed" gives a concrete use case, and "Only offered when backups are enabled for the organisation" is a real precondition the agent can check. It stops short of naming alternatives for the single-run or restore-point views, which is the only gap.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.