Skip to main content
Glama
Sign In
Agent Receipts

Agent Receipts

by webaesbyamin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_chain

Retrieve all receipts in a workflow chain ordered by timestamp. Use to audit complete multi-step agent workflows, calculate total cost and duration, or detect failed steps.

Instructions

Retrieve all receipts belonging to a chain, ordered by timestamp ascending to show the sequence of operations. A chain groups related receipts from a multi-step agent workflow. Returns the complete receipt objects for every step. Use to audit a complete workflow, calculate total chain cost and duration, or identify which step in a pipeline failed.

Input Schema

NameRequiredDescriptionDefault
chain_idYesThe chain ID to retrieve (format: "chain_" followed by 8 alphanumeric characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removedv0.2.11
  3. Changed1 schema field changedv0.2.10
    • changedInput schema / properties / chain_id / description
      Previous value: -"The chain ID to retrieve"New value: +"The chain ID to retrieve (format: \"chain_\" followed by 8 alphanumeric characters)"
  4. First observedv0.2.8

TDQS

A4.3/5.0
Behavior4/5

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

No annotations provided; description specifies ordering by timestamp ascending, returns complete receipt objects, and states it's read-only retrieval. Does not cover authentication or edge cases, but sufficient for typical use.

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?

Three sentences, first sentence front-loads action and resource, followed by context and use cases. No wasted words.

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?

No output schema but description explains return value (complete receipt objects) and ordering. For a single-param retrieval tool, all necessary context is present.

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 already covers the one parameter (chain_id) with format and example. Description adds no extra semantic value beyond stating it identifies the chain.

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?

The description clearly states the verb 'Retrieve' and the resource 'all receipts belonging to a chain', distinguishing it from sibling tools like get_receipt (single receipt) and list_receipts (filtered list).

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?

Explicit use cases are provided: audit workflow, calculate cost/duration, identify failed step. Lacks explicit exclusion guidance, but context is clear.

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

Deploy Server

Other Tools