Skip to main content
Glama
oliverames

YNAB MCP Server

by oliverames
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

List Budgets

list_budgets
Read-onlyIdempotent

Retrieve all available YNAB budgets with optional account details, providing budget IDs for use with other budget tools.

Instructions

List all budgets. Use a budget ID from the results in other tools, or omit budgetId to use the last-used budget.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeAccountsNoIf true, include each budget's account list in the response

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesStructured result returned by List Budgets.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changedv5.1.1
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / includeAccounts
      Added value: +{
+  "description": "If true, include each budget's account list in the response",
+  "type": "boolean"
+}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {
+      "description": "Structured result returned by List Budgets."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}
  2. First observedv2.0.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description's 'List all budgets' is consistent. However, the description adds no further behavioral context beyond the annotations, and the misleading parameter reference slightly detracts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description has two sentences; the first is concise and relevant, the second is confusing and unnecessary. It could be more focused on the actual parameter.

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

Completeness3/5

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

Given the simple tool with one optional boolean parameter and an output schema, the description partially explains the tool's purpose but fails to mention the includeAccounts parameter. The misleading reference to budgetId reduces completeness.

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 description coverage is 100% (1 parameter described), but the description does not explain the includeAccounts parameter. Instead, it introduces a non-existent budgetId parameter, which misleads about the tool's input requirements.

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 clearly states 'List all budgets' which is a specific verb and resource. However, it also mentions 'omit budgetId to use the last-used budget' despite budgetId not being a parameter in the schema. This introduces confusion and reduces clarity.

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?

The description attempts to guide usage by suggesting to use a budget ID from results, but the reference to 'omit budgetId' is misleading because budgetId is not a parameter. No explicit when-not-to-use or alternatives are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/oliverames/ynab-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server