Skip to main content
Glama

spending_report

Read-onlyIdempotent

Reads per-asset limits, current UTC-day settled amounts, outstanding commitments, and payment history to help agents monitor wallet spending against policy.

Instructions

Read persistent per-asset limits, current UTC-day settled amounts, outstanding commitments across all days, and payment history.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: limits are 'persistent', settled amounts are scoped to the 'current UTC-day', and commitments span 'across all days'. It does not disclose result size, ordering, or pagination behavior for a report that could be large.

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 sentence that front-loads the verb and then lists the returned data in a logical order. It is dense but every clause names a distinct data category. Slightly list-like, but no wasted words.

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?

With no parameters and no output schema, the description carries the burden of explaining what comes back, and it does name the four data categories. However, it says nothing about the shape of the response, whether history is truncated or paginated, or how per-asset results are keyed, which leaves real gaps for a multi-part report tool.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to compensate for. The description correctly signals that the call needs no input and returns everything in one shot.

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?

Opens with a specific verb ('Read') and enumerates the four resources returned: per-asset limits, UTC-day settled amounts, outstanding commitments, and payment history. That is far more specific than the name 'spending_report' alone. It stops short of a 5 because it does not contrast itself with the sibling check_balance, so an agent cannot fully disambiguate the two from the description.

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?

There is no when-to-use guidance, no prerequisite or exclusion statements, and no mention of the obvious alternative (check_balance) for simpler balance lookups. The agent must infer that this is the heavier, multi-dimensional reporting call rather than the quick balance check.

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