Skip to main content
Glama
Sign In
YNAB MCP Server

YNAB MCP Server

by oliverames
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get Money Movements By Month

get_money_movements_by_month
Read-onlyIdempotent

Fetch category budget reallocation history for a given month to track how funds moved between budget categories.

Instructions

Get category budget reallocation history for one month.

Input Schema

NameRequiredDescriptionDefault
monthYesYYYY-MM-DD, first of month, or 'current'
budgetIdNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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)"
    • changedInput schema / properties / month / description
      Previous value: -"Month in YYYY-MM-DD format (first of month), or 'current'"New value: +"YYYY-MM-DD, first of month, or 'current'"
    • 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 Money Movements By Month."
  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 Money Movements By Month."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}
  4. First observedv2.0.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world, and non-destructive behavior, so the safety profile is clear. The description adds that the results are historical and scoped to one month, but it does not discuss permissions, defaults, or edge cases.

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?

The definition is a single, front-loaded sentence with no wasted words. It is appropriately terse, though the most distinguishing concept ('by month') arrives at the end.

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 read-only tool with an output schema and rich annotations, the description still omits how it differs from similarly named money-movement tools and what budgetId does when supplied or omitted. Those omissions are material because the sibling list contains closely related alternatives.

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?

Schema coverage is only 50%, and the description adds no meaning beyond the already-documented month parameter. The optional budgetId parameter remains undocumented in both the schema and the description, so the description fails to compensate for the coverage gap.

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 gives a specific verb and resource: 'Get category budget reallocation history' with a clear scope of 'for one month.' It is more specific than the tool name alone, but it does not explicitly distinguish this tool from siblings like list_money_movements or get_money_movement_groups_by_month.

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 tool versus alternatives, nor are any conditions or prerequisites stated. An agent must infer usage entirely from the name and one-line purpose.

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