Skip to main content
Glama

list_receipts

Query and paginate receipts from SQLite storage with filters like agent, action, status, and more. Sort by timestamp or cost to audit agent activity or generate reports.

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?

With no annotations provided, the description adequately discloses behavior: it reads from local SQLite storage, returns paginated results with count and navigation flags, and specifies default sorting and limit. It does not cover all edge cases (e.g., empty results) but is thorough for a list tool.

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?

The description comprises four well-structured sentences, each conveying essential information: core action, sorting, output, and defaults/use cases. No redundant or missing content.

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?

Given the complexity (10 parameters, no output schema), the description covers core functionality, pagination details, and use cases. It does not describe the receipt structure, but that is likely known from context; still sufficiently complete for tool selection.

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 coverage is 100%, and the description repeats some parameter info but adds context on sorting format and defaults. However, the schema already describes parameters well, so the added value is marginal.

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 it queries and paginates receipts with filtering and sorting, and specifies use cases like auditing and report generation. It distinctively focuses on listing multiple receipts, differentiating from siblings like get_receipt (single) and generate_invoice.

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?

The description explicitly tells when to use the tool ('Use to audit agent activity, generate reports, or find specific receipts'). It does not mention when not to use it or alternatives, but the context is clear given siblings.

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