Skip to main content
Glama
Sign In
YNAB MCP Server

YNAB MCP Server

by oliverames
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get Scheduled Transaction

get_scheduled_transaction
Read-onlyIdempotent

Retrieve a scheduled transaction's date, frequency, dollar amount, payee, and category by ID, stripping composite ID date suffixes so recurring transaction details are clear.

Instructions

Get scheduled date, frequency, dollar amount, payee and category. Strip composite ID date suffixes or use get_transaction.

Input Schema

NameRequiredDescriptionDefault
budgetIdNo
scheduledTransactionIdYesScheduled transaction ID

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv6.1.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / budgetId / description
      Removed value: -"Budget ID (uses default if not provided)"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv5.4.0
    • removedOutput schema / properties / result / description
      Removed value: -"Structured result returned by Get Scheduled Transaction."
  3. Changed1 schema field changedv5.1.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {
+      "description": "Structured result returned by Get Scheduled Transaction."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}
  4. First observedv2.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds a useful behavioral note about handling composite ID date suffixes, but it does not explain error behavior or what happens with unknown IDs.

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?

Two tightly packed sentences with the field list front-loaded and no filler. The second sentence is slightly cryptic but still earns its place as usage guidance.

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?

An output schema exists, so return-value explanations are not needed, and annotations cover the safety profile. The description lists key fields and mentions ID handling, though it leaves budgetId unexplained for a tool with 2 parameters.

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 50%: scheduledTransactionId has only a minimal 'Scheduled transaction ID' description, and budgetId is undocumented. The description adds a hint about composite ID suffixes, which gives extra meaning to the ID parameter, but it does not compensate for the undocumented budgetId.

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 retrieval action and enumerates the returned fields (scheduled date, frequency, dollar amount, payee, category), making clear it fetches a scheduled transaction's details. It distinguishes itself from the sibling get_transaction explicitly. The verb 'Get' is generic but the resource and output fields compensate.

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?

It names the alternative get_transaction, which is helpful, but the condition ('Strip composite ID date suffixes') is cryptic and does not explain when to prefer this tool versus list_scheduled_transactions or get_transaction. Usage is implied rather than clearly stated.

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

Deploy Server

Other Tools