py-ynab-mcp

Overview Schema Source Related Servers Discussions Admin

list_payees

Retrieve all payees for a YNAB budget, including names and IDs. Optionally specify a budget ID; defaults to the default budget.

Instructions

List all payees for a YNAB budget.

Returns payee names and IDs.

Args: budget_id: Budget ID to list payees for. If not provided, uses the default budget.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_payees"
  }
}

Input Schema

Name	Required	Description	Default
`budget_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 12, 2026

TDQS

A4.6/5.0

Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses the default budget behavior, which is a key behavioral trait. It does not mention side effects, but as a read-only list operation, the absence is acceptable.

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 extremely concise with three short sentences. It front-loads the core purpose and adds parameter details efficiently, with no unnecessary words.

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

Completeness5/5

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

For a simple list tool with one optional parameter and an output schema, the description is complete. It explains the return content and parameter usage, requiring no additional context.

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

Parameters5/5

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

The description provides meaningful explanation for the budget_id parameter beyond the schema, including its purpose and the default behavior when omitted. This compensates for 0% schema description coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it lists all payees for a YNAB budget and returns payee names and IDs. It distinguishes from sibling tools like list_accounts or get_payee by specifying its exact resource and action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the optional budget_id and default behavior, but lacks explicit guidance on when to use this tool versus alternatives like get_payee. However, the purpose is straightforward for a list-all operation.

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