Skip to main content
Glama

execution_receipt_get

Retrieve a durable local execution receipt by directory and receipt ID to inspect workflow, batch, or watcher status and results without exposing PDF contents or recipe parameters.

Instructions

Query durable local workflow, batch or watcher execution receipts; no PDF contents or recipe parameters are stored

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": {
      "directory": "<directory>",
      "receipt_id": "<receipt_id>"
    },
    "name": "execution_receipt_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
directoryYes
receipt_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does add one useful disclosure — receipts are durable and local, and neither PDF contents nor recipe parameters are retained — which tells the agent what data will be absent from results. It says nothing about read-only vs mutating behavior, permissions, error handling for a missing receipt_id, or the shape of a receipt.

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 front-loaded sentence with a semicolon clause; no filler. It is efficient, though the second clause is arguably a caveat that would read better as a separate, labeled sentence.

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

Completeness2/5

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

With no annotations, no output schema, and zero parameter documentation, the definition leaves too much unspecified for a tool that takes a required receipt_id and a limit. It never states what a receipt record contains, whether results are paginated, or what happens when the id is unknown.

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?

Schema description coverage is 0%, so all three parameters (directory, receipt_id, limit) are undocumented in structured fields. The description compensates only weakly: "durable local" hints that directory is a local filesystem path, but receipt_id, limit, and the 1–1000 range are left entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb ("Query") and a resource ("durable local workflow, batch or watcher execution receipts"), which is more specific than the bare name. However, "Query" is ambiguous between retrieving one record and listing many, and the sibling execution_receipt_list is never referenced, so an agent cannot tell from the description alone which of the two to pick.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no mention of the obvious alternative execution_receipt_list. The agent must infer from the name and the required receipt_id that this is the single-record variant.

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