Skip to main content
Glama
make-cents-please

make-cents-please

by hopkeno

ynab_get_scheduled_transaction

Read-only

Retrieve one scheduled transaction from a YNAB plan by its ID to review amounts, dates, and recurrence details before they post.

Instructions

Get one scheduled transaction.

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": {
      "scheduled_transaction_id": "<scheduled_transaction_id>"
    },
    "name": "ynab_get_scheduled_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idNoPlan (budget) id from ynab_list_plans. Omit to use the configured default plan.
scheduled_transaction_idYesId from ynab_list_scheduled_transactions.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no note on behavior for an unknown id, no indication of the configured-default-plan fallback, and no mention of data freshness or scope of the returned record.

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 short sentence with no wasted words and the core purpose front-loaded. It is efficient but so terse that it borders on under-specification rather than optimal concision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Because an output schema exists, return values need not be explained, and the annotations cover safety. Still, for a lookup tool whose main failure mode is a missing or wrong id, the description offers no behavioral context, and it omits the plan_id default-plan semantics that the schema happens to document.

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% and both parameters carry their own descriptions, including the cross-reference to ynab_list_scheduled_transactions and the omit-for-default-plan rule. Baseline 3 applies since the description contributes no additional parameter meaning.

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

Purpose3/5

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

The description states a specific verb and resource ("Get one scheduled transaction"), and the word "one" implies single-record retrieval versus the sibling list tool. However, it is essentially a restatement of the tool name and adds no scope detail beyond that.

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 guidance on when to use this versus ynab_list_scheduled_transactions or ynab_get_transaction, and no prerequisites such as needing an id from the list tool mentioned in prose. Usage must be inferred entirely from the name and schema.

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