Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Getscheduledtransactions

getScheduledTransactions

Retrieves all scheduled transactions for a YNAB plan, optionally returning only entries changed since a given server knowledge value to support efficient syncing.

Instructions

Returns all scheduled transactions

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": {
      "plan_id": "<plan_id>"
    },
    "name": "getScheduledTransactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesThe id of the plan. "last-used" can be used to specify the last used plan and "default" can be used if default plan selection is enabled (see: https://api.ynab.com/#oauth-default-plan).
last_knowledge_of_serverNoThe starting server knowledge. If provided, only entities that have changed since `last_knowledge_of_server` will be included.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and discloses almost nothing: no mention that results are plan-scoped, no mention of pagination or the delta-sync behavior enabled by last_knowledge_of_server, and no note about authentication requirements. Only the fact that the set is unfiltered ("all") is conveyed.

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 that is front-loaded and free of filler. It is efficient, though its brevity borders on under-specification for a delta-capable listing endpoint.

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?

The tool supports incremental sync via last_knowledge_of_server and requires a plan identifier, yet the description says nothing about either behavior, and there is no output schema to explain the return shape. For a two-parameter, annotation-free endpoint, this leaves the agent under-informed.

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 description coverage is 100%, so both plan_id (including the "last-used"/"default" sentinels) and last_knowledge_of_server are fully documented in the schema. The description adds no meaning beyond that, so the baseline 3 applies.

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?

"Returns all scheduled transactions" gives a specific verb (returns) and resource (scheduled transactions), and the word "all" signals a collection listing rather than a single-entity lookup, which implicitly separates it from getScheduledTransactionById. It stops short of any explicit sibling differentiation or scope statement (e.g. per-plan, current vs. past).

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 choose this over getScheduledTransactionById or getTransactions, and no note about prerequisites such as needing a plan_id. The agent must infer usage purely 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.