Skip to main content
Glama

spending_report

Read-only

Generate spending and rewards reports by category and card for a chosen date range; when dates are omitted, it covers the current calendar month.

Instructions

Spending and rewards by category and by card. With no dates, covers the current calendar month.

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": "spending_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoYYYY-MM-DD, inclusive
startNoYYYY-MM-DD, inclusive

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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, so the description only needs to add context. It does add one behavioral fact beyond the annotations and schema: what happens when no date range is supplied. It says nothing about aggregation granularity (is it a category-by-card cross-tab?) or whether the rewards figures are estimates, which is where the remaining ambiguity sits.

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?

Two short sentences with zero filler, and the most decision-relevant fact (the default month window) is placed where it is read immediately after the scope statement.

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 read-only, two-optional-parameter report with an output schema, the definition covers scope, breakdown dimensions, and the default time window — enough to call it correctly. The only gap is what the report actually aggregates (per-category, per-card, or both combined), which the output schema presumably resolves.

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% — both start and end are documented as inclusive YYYY-MM-DD dates with a null default. The description adds the meaning of that null default (current calendar month), which is genuine value, but it does not clarify open cases such as a start without an end or an end without a start. Baseline 3 with a small lift is appropriate.

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 names the resource (spending and rewards) and its two breakdown dimensions (by category, by card), which is specific enough that an agent can distinguish it from list_purchases (raw transactions) or rewards_balance (a point total). It lacks a verb and does not explicitly name a sibling it is not, so it stops just short of 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?

The one piece of usage guidance is the default window: no dates means the current calendar month. That is helpful, but there is no statement of when to prefer this over rewards_balance or list_purchases, and no exclusions. Usage is implied rather than directed.

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