Skip to main content
Glama
Meh-S-Eze

MCP YNAB Server

set_preferred_budget_id

Define your primary YNAB budget ID to streamline account balance checks, transaction data access, and new transaction creation within the MCP YNAB Server.

Instructions

Set the preferred YNAB budget ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
budget_idYes

Implementation Reference

  • The MCP tool handler function for 'set_preferred_budget_id', decorated with @mcp.tool(), which delegates to the YNABResources helper method and returns a confirmation message.
    @mcp.tool()
    async def set_preferred_budget_id(budget_id: str) -> str:
        """Set the preferred YNAB budget ID."""
        ynab_resources.set_preferred_budget_id(budget_id)
        return f"Preferred budget ID set to {budget_id}"
  • Helper method in the YNABResources class that sets the preferred budget ID in memory and persists it to a configuration file (PREFERRED_BUDGET_ID_FILE).
    def set_preferred_budget_id(self, budget_id: str) -> None:
        """Set the preferred budget ID."""
        self._preferred_budget_id = budget_id
        with open(PREFERRED_BUDGET_ID_FILE, "w") as f:
            f.write(budget_id)
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states this is a 'set' operation (implying mutation), but doesn't disclose whether this changes global preferences, requires specific permissions, has side effects, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is inadequate.

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, direct sentence with zero wasted words. It's front-loaded with the core action and resource, making it highly efficient for quick comprehension.

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 0% schema description coverage, the description is insufficient. It doesn't explain what 'preferred' means in context, how this affects other operations, or what the user should expect after invocation. The simplicity of the tool (1 parameter) doesn't compensate for these gaps.

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 description coverage is 0%, so the description must compensate but doesn't add parameter details. It mentions 'budget_id' implicitly but provides no context about format, source, or validation. With only one parameter, the baseline is 4, but the lack of any parameter guidance reduces this to 3.

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 action ('Set') and the target resource ('preferred YNAB budget ID'), making the purpose immediately understandable. It doesn't distinguish from siblings like 'get_budgets' or 'create_transaction', but the verb+resource combination is specific enough for basic understanding.

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?

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing existing budgets), exclusions, or relationships to sibling tools like 'get_budgets' for listing available budgets first.

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/Meh-S-Eze/ynab-mcp-client2'

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