Skip to main content
Glama

list_receipts

Query signed AI agent receipts to audit activity and track operations. Filter by agent, status, or environment with pagination and sorting by timestamp, cost, or latency for comprehensive reporting and accountability.

Instructions

Query and paginate receipts from local SQLite storage with optional filtering by agent, action, status, environment, type, chain, or tag. Supports sorting by timestamp, cost, or latency. Returns paginated results with total count, page info, and has_next/has_prev flags. Default: 50 receipts per page, sorted by timestamp descending. Use to audit agent activity, generate reports, or find specific receipts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idNoFilter by agent ID (exact match)
actionNoFilter by action name (exact match)
statusNoFilter by status: "pending", "completed", "failed", or "timeout"
environmentNoFilter by environment: "development", "production", "staging", or "test"
receipt_typeNoFilter by type: "action", "verification", "judgment", or "arbitration"
chain_idNoFilter to receipts in a specific chain
tagNoFilter to receipts containing this tag
pageNoPage number, starting at 1 (default: 1)
limitNoResults per page, 1 to 100 (default: 50)
sortNoSort field and direction in format "field:asc" or "field:desc" (e.g., "timestamp:desc", "cost_usd:asc")
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses local SQLite storage (persistence layer), pagination mechanics (default 50/page, has_next/has_prev flags), and return structure (total count, page info). Missing explicit read-only safety declaration, though implied by 'Query'.

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 with zero waste: first defines core functionality and filters, second covers pagination/defaults/returns, third provides use cases. Information is front-loaded and dense.

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

Completeness4/5

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

For a 10-parameter tool with no annotations or output schema, the description compensates well by detailing pagination behavior, filter combinations, and return flags. Minor gap: could specify what fields appear in the receipt objects returned.

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

Parameters4/5

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

Schema coverage is 100%, establishing baseline 3. Description adds value by enumerating valid sort fields ('timestamp, cost, or latency') not explicitly listed in the schema's sort parameter description, helping agents construct valid sort strings.

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?

Excellent specificity: states exact verb ('Query and paginate'), resource ('receipts from local SQLite storage'), and scope (optional filtering by 7 dimensions). Distinguishes from sibling get_receipt by emphasizing multiple results and filtering.

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?

Provides clear positive guidance ('Use to audit agent activity, generate reports, or find specific receipts') establishing appropriate contexts. However, lacks explicit negative guidance or contrast with sibling get_receipt for single-record lookups.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/webaesbyamin/agent-receipts'

If you have feedback or need assistance with the MCP directory API, please join our Discord server