Skip to main content
Glama

Confirm a forecast transaction

confirm_forecast

Marks one forecast transaction as really happened (like the ✓ button in the app), optionally with the real amount and date. Only forecasts dated today or earlier can be confirmed (list_upcoming returns them). A different amount does not change the recurring item the forecast comes from; that is updated in the app. It can be undone from the app (Ctrl+Z).

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": {
      "transaction_id": "<transaction_id>"
    },
    "name": "confirm_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookNoAccount book id (from list_books). Optional if the user has only one.
dateNoReal date (today or earlier). Default: the forecast date.
amountNoReal amount, positive (the sign is kept). Default: the forecast amount.
transaction_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare a non-destructive write, and the description adds real value on top: it discloses that a differing amount does NOT propagate to the recurring item, and that the action can be reversed via Ctrl+Z in the app. The one omission is idempotency — annotations say idempotentHint=false but the description never says what a repeat confirmation does.

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?

Three tight sentences ordered sensibly: what it does, the eligibility constraint with a pointer to the discovering tool, then side-effect and reversibility caveats. No filler, though the parenthetical Ctrl+Z reference is slightly app-centric for an API consumer.

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 4-parameter mutation with no output schema, the description covers purpose, precondition, side-effect scoping and undo, which is substantial. It stops short of saying what the call returns and how a duplicate confirmation behaves, both of which matter for a non-idempotent write.

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 75% and the schema already documents defaults and the sign convention for amount, so it does most of the work. The description adds one genuine nuance beyond it — that passing a different amount leaves the underlying recurring item untouched — but adds nothing about the 'book' parameter or the transaction_id semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'Marks one forecast transaction as really happened' — and anchors it to a familiar UI action (the ✓ button). The singular scope ('one') and the optional real amount/date make it clearly distinct from add_transaction or list_upcoming.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit eligibility rule ('Only forecasts dated today or earlier can be confirmed') and routes the agent to list_upcoming as the source of eligible ids. It does not state explicitly when to prefer this over add_transaction for a transaction that actually occurred, so a small inference remains.

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