Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Createscheduledtransaction

createScheduledTransaction

Create a future-dated transaction in a YNAB plan by specifying account, date, amount, payee, and optional recurrence frequency.

Instructions

Creates a single scheduled transaction (a transaction with a future date).

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>",
      "scheduled_transaction": "<scheduled_transaction>"
    },
    "name": "createScheduledTransaction"
  }
}

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).
scheduled_transactionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about authentication, that the call persists a new resource, whether re-scheduling or duplication occurs, or what the response contains. The only added detail, that the date is in the future, is already documented on the date property in the schema.

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 well-formed sentence with the core action front-loaded and no wasted words. Brevity here edges toward under-specification rather than padding, which is preferable, but it does leave obvious gaps.

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?

For a mutation tool with no annotations, no output schema, and a nested object with numerous constrained fields, the definition is thin. An agent gets no signal about side effects, required plan/account context, or return shape, which is a meaningful gap for a write operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 50% schema coverage and a nested scheduled_transaction object containing many domain-specific fields (milliunits amount, frequency enum, payee resolution), the description explains none of it. Guidance on payee vs payee_name resolution, milliunit amounts, or unsupported split/credit-card-payment categories would have been valuable and is absent.

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?

The description states a specific verb and resource ("Creates a single scheduled transaction") and the parenthetical clarifies that a scheduled transaction is a transaction dated in the future, which implicitly distinguishes it from the sibling createTransaction. It stops short of naming createTransaction explicitly, so an agent must infer the boundary rather than being told it.

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 explicit when-to-use guidance, no prerequisites (plan selection, account requirements), and no mention of the alternative createTransaction for immediate transactions. The future-date clause only hints at the distinction, leaving the agent to infer it from the title.

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