Skip to main content
Glama

List expenses

list_expenses
Read-only

List the business's expenses. Filter by search text, date range, amount, activity, booking, or guide.

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_expenses"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoSearch vendor, description, category, activity, booking, or guide.
endNoOnly expenses spent on or before this date.
limitNo
startNoOnly expenses spent on or after this date.
offsetNo
guide_idNo
booking_idNo
max_amountNoMaximum amount in cents.
min_amountNoMinimum amount in cents.
activity_idNo
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. Beyond that the description adds nothing: no result ordering, no default page size or pagination behavior despite limit/offset existing, and no note on how the optional business_id resolves when the connection covers a single business.

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?

Two sentences, zero filler, with the core action stated first and the filter list second. The second sentence leans heavily on restating schema fields, which keeps it from being maximally efficient.

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

Completeness3/5

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

For an eleven-parameter list tool with no output schema, the definition covers the filtering surface but is silent on pagination, total counts, and result ordering — details an agent needs to page correctly. It is adequate but leaves material gaps.

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?

At 55% schema coverage the description does useful work by grouping the filter families (text, date range, amount range, activity, booking, guide), which maps to seven of the eleven parameters. It leaves limit, offset, business_id, and amount units unexplained, so it only partially compensates for the coverage gap.

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?

The description states a specific verb+resource ("List the business's expenses") and enumerates the filter dimensions, so an agent knows exactly what it retrieves. It does not distinguish itself from nearby siblings such as get_expense (single record) or get_finance_summary, which keeps it below a 5.

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?

"Filter by search text, date range, amount, activity, booking, or guide" implies the retrieval scenarios (browse/search expenses) but never states when to use this versus get_expense or get_finance_summary, and gives no exclusions or prerequisites. Usage is inferable rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources