Skip to main content
Glama

execution_receipt_list

Query durable local execution receipts for workflows, batches, or watchers to audit past runs. Filter by directory or receipt ID and cap results with a limit.

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>"
    },
    "name": "execution_receipt_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
directoryYes
receipt_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It usefully discloses a negative guarantee — receipt records hold no PDF contents or recipe parameters — which sets expectations about payload size and sensitivity. It does not say whether the operation is read-only, how results are ordered, whether the directory is scanned recursively, or how limit and receipt_id interact, leaving meaningful gaps.

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 the resource and scope first and the storage caveat second. Every clause carries information; the semicolon clause about excluded content is the one piece that might arguably belong in an output description, but there is no output schema to hold it.

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?

This is a list tool with a required path parameter, paging limit, and an optional filter, yet there is no output schema, no annotations, and no description of return fields, ordering, or paging behavior. An agent knows what the tool queries but not what a result looks like or how to page through more than the default 50 records, which is a substantive gap for a collection endpoint.

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 the description is the only source of parameter meaning, and it does not explain any of the three parameters. 'directory' is unqualified (which directory — the receipt store root?), 'receipt_id' is never mentioned (does it filter to one receipt, or conflict with listing?), and 'limit' defaults are known only from the schema. Only a weak inference is available: receipts are 'local', so directory plausibly locates the receipt store.

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 ('Query ... execution receipts') and scopes it to three execution kinds (workflow, batch, watcher), which lets an agent distinguish it from the singular execution_receipt_get sibling. It stops short of an explicit contrast sentence, but the resource and scope are 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?

The qualifiers 'durable local' and the enumeration of workflow/batch/watcher receipts imply the situation in which this tool applies, but there is no explicit statement of when to use it versus execution_receipt_get or what happens when a receipt_id is supplied. Usage must be inferred from the resource description rather than read directly.

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