Skip to main content
Glama

List upcoming expenses

list_upcoming_expenses
Read-only

List active upcoming and recurring expenses for a ledger. If month is given, only items with occurrences in that month are returned. Amounts in currency units, not cents.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ledger_id": "<ledger_id>"
    },
    "name": "list_upcoming_expenses"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthNoOptional month YYYY-MM to filter to occurrences in that month.
ledger_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value with 'active' scoping (filtering out inactive items) and the units caveat ('Amounts in currency units, not cents'), but says nothing about ordering, result size, or recurring-occurrence aggregation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with purpose, with no filler. The second sentence largely restates what the month parameter's schema description already says, so it does not fully earn its place.

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 a simple two-parameter read tool with annotations covering safety, the definition covers purpose, filtering and amount units. It leaves gaps on return shape (what fields an 'upcoming expense' has), ordering, and whether recurring items are expanded per occurrence — relevant since there is no output schema.

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 only 50%: month is fully documented in the schema, while ledger_id has no description anywhere. The description compensates partially by tying the list to a ledger and clarifying that month filters on occurrence dates, but adds no format or validation detail beyond the pattern already in the schema.

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?

States a specific verb and resource ('List active upcoming and recurring expenses') plus the required scope ('for a ledger'), which clearly separates it from the write-side sibling add_upcoming_expense. It never names an alternative explicitly, so sibling differentiation is only implicit.

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 month clause describes conditional filtering behavior rather than when to choose this tool over alternatives. There is no guidance on when to omit month, how results are ordered, or what to do if the ledger has no upcoming items.

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