Skip to main content
Glama

list_purchases

Read-only

Retrieve purchases newest first, with optional filters for date range, card, category, merchant, and result limit.

Instructions

Show purchases, newest first, optionally filtered.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_purchases"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoUp to this date (YYYY-MM-DD), inclusive
cardNoCard id or name
limitNo
startNoFrom this date (YYYY-MM-DD), inclusive
categoryNo
merchantNoPart of the merchant name

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds the one genuinely new behavioral fact — results are ordered newest first — but says nothing about the default 20-item cap constraining results, how multiple filters combine, or whether pagination is needed to see all purchases.

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 no filler. It is lean to the point of under-specification, but no sentence is wasted.

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 six parameters, a default limit of 20, and a silent 500 maximum, a one-line description leaves too much unsaid for an agent to call this correctly or interpret truncated results. The output schema covers return shape, so that gap is excusable, but the filtering and result-cap behavior are not.

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 67%, with card/start/end/merchant documented but category and limit left bare. The description mentions filtering generically without mapping it to the specific filter fields, and adds no meaning for limit; the only extra semantic value is the sort order, which the schema never states.

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?

"Show purchases" names a specific verb and resource and adds the ordering guarantee ("newest first"), so the agent knows this is a read/list operation. It does not distinguish itself from nearby read siblings such as spending_report, leaving some ambiguity about listing vs. aggregation.

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?

"Optionally filtered" only implies that filters exist and are optional; there is no statement of when to use this tool versus spending_report or card_details, and no exclusions or preconditions. The agent must infer routing from the name alone.

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