Skip to main content
Glama

Upcoming and overdue forecast transactions

list_upcoming
Read-onlyIdempotent

Forecast (not yet confirmed) transactions: the overdue ones (date already passed, waiting to be confirmed against the bank) and the ones due in the next days days (bills, salaries, renewals). Each row has the id that confirm_forecast accepts.

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

Input Schema

NameRequiredDescriptionDefault
bookNoAccount book id (from list_books). Optional if the user has only one.
daysNoDays ahead (default 30).
overdue_daysNoHow far back to look for overdue unconfirmed forecasts (default 60).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds real behavioral context beyond them: that these rows are unconfirmed forecasts, that 'overdue' means the date has passed and is awaiting bank confirmation, and that the returned id is the handoff key for confirm_forecast.

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 tight sentences with the core definition first and the confirm_forecast handoff last; every clause carries information (scope, categories, row id) and nothing is padded or repeated.

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?

There is no output schema, so the description bears the burden of describing results; it only notes that rows carry an id, saying nothing about what else a row contains (amount, due date, payee), ordering, or result limits. For a read-only list tool of low complexity this is workable but leaves a clear gap.

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?

Schema coverage is 100%, so the schema already documents `book`, `days` and `overdue_days` with defaults and bounds. The description still contributes meaning by explaining what is being counted inside `days` (bills, salaries, renewals) and what 'overdue' means for the overdue lookback window, rather than restating the fields.

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 resource (forecast, not-yet-confirmed transactions) and enumerates its two components: overdue items awaiting bank confirmation and items due within `days`. An agent can tell this apart from plain transaction search, though it never contrasts itself with the sibling `get_forecast`, which sounds closely related.

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?

Usage is implied rather than stated: the mention that 'Each row has the id that confirm_forecast accepts' quietly routes the agent to the confirmation tool after listing. There is no explicit when-to-use versus `get_forecast` or `search_transactions`, and no when-not guidance.

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