Skip to main content
Glama

get_run

Read-onlyIdempotent

Read your execution status, output and append-only settlement events. A schema-valid output still needs buyer quality verification.

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

Input Schema

NameRequiredDescriptionDefault
run_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description still adds real content: it enumerates what is returned (status, output, append-only settlement events) and warns that schema validity does not equal buyer-verified quality — a caveat annotations cannot express.

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?

Two short sentences, front-loaded with the return payload and followed by the caveat; nothing is padding. The second sentence is terse to the point of ambiguity about what the agent should do with the warning, which keeps it from a 5.

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?

With no output schema, the description carries the burden of describing return values, and it does so only at a high level (status, output, settlement events) without structure, ordering, or volume/pagination hints. For a simple one-parameter read tool that is serviceable but leaves gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter, run_id, with 0% schema description coverage, and the description says nothing about its format, origin, or whether the run must belong to the caller. 'your execution' hints at ownership but does not compensate for the undocumented parameter.

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 opens with a specific verb and resource: 'Read your execution status, output and append-only settlement events.' That distinguishes it from list_runs (collection-level) and from lifecycle mutations like complete_run or accept_run. It never names run_id explicitly, but 'your execution' plus the schema makes the scope unambiguous.

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: this is the read-back tool you call after starting/claiming a run. The second sentence adds a workflow caveat (a schema-valid output is not a quality-verified delivery), which nudges toward accept_delivery/dispute_delivery, but no alternative is named and no when-not-to-use condition is stated.

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.

Resources