Skip to main content
Glama
Jtewen

You Need A Budget (YNAB) MCP

by Jtewen

list-scheduled-transactions

View all upcoming scheduled transactions for your budget to forecast and manage bills effectively. Works with YNAB to enhance financial planning and control.

Instructions

List all upcoming scheduled transactions for a given budget. Useful for forecasting upcoming bills.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
budget_idNoThe ID of the budget. If not provided, the default budget will be used.

Implementation Reference

  • Handler logic for executing the 'list-scheduled-transactions' tool. Retrieves scheduled transactions via ynab_client and returns a formatted text list.
    elif name == "list-scheduled-transactions":
        budget_id = await _get_budget_id(arguments)
        transactions = await ynab_client.get_scheduled_transactions(budget_id=budget_id)
    
        if not transactions:
            return [types.TextContent(type="text", text="No scheduled transactions found.")]
    
        scheduled_list = "\n".join(
            f"- {t.var_date}: {t.payee_name or 'N/A'} | "
            f"{t.category_name or 'N/A'} | {t.amount / 1000:.2f} "
            f"(Frequency: {t.frequency})"
            for t in transactions
        )
        return [
            types.TextContent(
                type="text",
                text=f"Here are the scheduled transactions:\n{scheduled_list}",
            )
        ]
  • YNABClient helper method that calls the YNAB API to fetch scheduled transactions for a budget.
    async def get_scheduled_transactions(
        self, budget_id: str
    ) -> list[ynab.ScheduledTransactionDetail]:
        response = await self._run_sync(
            self._scheduled_transactions_api.get_scheduled_transactions,
            budget_id
        )
        return response.data.scheduled_transactions
  • Tool registration in list_tools() handler, defining name, description, and input schema.
    types.Tool(
        name="list-scheduled-transactions",
        description="List all upcoming scheduled transactions for a given budget. Useful for forecasting upcoming bills.",
        inputSchema={
            "type": "object",
            "properties": {
                "budget_id": {
                    "type": "string",
                    "description": "The ID of the budget. If not provided, the default budget will be used.",
                }
            },
        },
    ),
  • Input schema definition for the list-scheduled-transactions tool.
    inputSchema={
        "type": "object",
        "properties": {
            "budget_id": {
                "type": "string",
                "description": "The ID of the budget. If not provided, the default budget will be used.",
            }
        },
  • Includes 'list-scheduled-transactions' in the set of read-only tools.
    READ_ONLY_TOOLS = {
        "list-budgets",
        "list-accounts",
        "list-transactions",
        "list-categories",
        "list-payees",
        "list-scheduled-transactions",
        "get-financial-overview",
        "get-month-info",
        "lookup-payee-locations",
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the tool is 'useful for forecasting,' which adds some context, but fails to describe key behaviors such as whether it returns all scheduled transactions or is paginated, what format the output is in, or any rate limits or permissions required. This leaves significant gaps in understanding how the tool behaves.

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 two sentences, front-loaded with the core purpose and followed by a brief usage hint. Every sentence adds value without redundancy, making it efficiently structured and appropriately sized for the tool's complexity.

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 low complexity (one optional parameter, no output schema, no annotations), the description is minimally adequate. It covers the purpose and a usage hint, but lacks details on output format, behavioral traits, or differentiation from siblings. For a simple list tool, this is acceptable but leaves room for improvement in completeness.

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?

The input schema has 100% description coverage, with the 'budget_id' parameter well-documented in the schema itself. The description does not add any additional meaning or details about parameters beyond what the schema provides, such as format examples or constraints. Given the high schema coverage, the baseline score of 3 is appropriate as the description does not compensate but also does not detract.

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 ('upcoming scheduled transactions for a given budget'), making the purpose specific and understandable. However, it does not explicitly differentiate from sibling tools like 'list-transactions' or 'manage-scheduled-transaction', which could handle similar data, so it misses the top score.

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?

The description includes 'Useful for forecasting upcoming bills,' which implies a context for when to use this tool, but it does not provide explicit guidance on when to choose this over alternatives like 'list-transactions' or 'manage-scheduled-transaction.' No exclusions or prerequisites are mentioned, leaving usage somewhat vague.

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