Skip to main content
Glama

Get data run

get_data_run
Read-only

Show one backup, restore or clone run with every attempt of every step - the step key, job, status, failure class and error excerpt. This is what explains why a backup failed. Discover run ids with list_data_runs. Read-only. Only offered when backups are enabled for the organisation.

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

Input Schema

NameRequiredDescriptionDefault
run_idYesRun id (UUID) from list_data_runs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description still adds real context by disclosing the depth of the response (per-attempt, per-step detail with failure class and error excerpt) and an availability precondition. Return format is sketched but not exhaustively specified.

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?

Four short sentences, front-loaded with what is returned, then the diagnostic purpose, the id source, and the precondition. No redundant wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-item read tool with one required parameter and no output schema, the description supplies the purpose, the id source, the shape of the returned data, and an availability constraint — everything an agent needs to call it correctly.

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 coverage is 100% and the single run_id parameter is already documented in the schema. The description only reinforces the source of the id by pointing at list_data_runs, so the baseline of 3 applies.

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 ("Show one backup, restore or clone run") and enumerates the payload (every attempt of every step, step key, job, status, failure class, error excerpt), which makes it unmistakable next to list_data_runs.

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?

Explicitly frames the use case ("This is what explains why a backup failed") and routes id discovery to list_data_runs. It gives a precondition (backups enabled for the organisation) but no explicit when-not guidance.

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.