Skip to main content
Glama
Jtewen

You Need A Budget (YNAB) MCP

by Jtewen

list-budgets

Retrieve all active YNAB budgets to view or manage your financial plans directly through the MCP server for AI-powered budgeting control.

Instructions

List all available YNAB budgets

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for executing the "list-budgets" tool. It retrieves all YNAB budgets using the ynab_client and formats a markdown-style list of budget names and IDs.
    if name == "list-budgets":
        budgets = await ynab_client.get_budgets()
    
        if not budgets:
            return [types.TextContent(type="text", text="No budgets found.")]
    
        budget_list = "\n".join(f"- {b.name} (ID: {b.id})" for b in budgets)
    
        return [
            types.TextContent(
                type="text",
                text=f"Here are your available budgets:\n{budget_list}",
            )
        ]
  • The registration of the "list-budgets" tool in the handle_list_tools() function, which lists available tools for the MCP server.
    types.Tool(
        name="list-budgets",
        description="List all available YNAB budgets",
        inputSchema={"type": "object", "properties": {}},
  • The input schema for the "list-budgets" tool, which requires no parameters (empty object). Note: output is not explicitly schemed but returns TextContent.
    inputSchema={"type": "object", "properties": {}},
  • "list-budgets" is included in the READ_ONLY_TOOLS set, allowing it in read-only mode.
    "list-budgets",
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states the action ('List all available') but doesn't describe return format, pagination, sorting, error conditions, or authentication requirements. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple list operation and front-loads the essential information. Every word earns its place.

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 tool's simplicity (zero parameters, no output schema), the description is minimally adequate but lacks completeness. Without annotations or output schema, it should ideally mention what 'list' returns (e.g., budget objects with IDs/names) or behavioral aspects. It meets basic requirements but leaves room for improvement.

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

Parameters4/5

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

The tool has zero parameters (schema coverage 100%), so no parameter documentation is needed. The description appropriately doesn't mention parameters, and the baseline for zero parameters is 4. No additional semantic value could be added beyond what's already covered by the empty schema.

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 clearly states the verb ('List') and resource ('YNAB budgets'), making the purpose immediately understandable. It doesn't explicitly distinguish from siblings like 'list-accounts' or 'list-categories', but the resource specificity ('budgets') provides implicit differentiation. The description avoids tautology by not just restating the tool name.

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 provides no guidance on when to use this tool versus alternatives. With siblings like 'lookup-entity-by-id' and 'manage-budgeted-amount', there's no indication whether this tool is for browsing all budgets versus specific operations. No prerequisites, exclusions, or comparative context are mentioned.

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

Related 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/Jtewen/ynab-mcp'

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