Skip to main content
Glama
make-cents-please

make-cents-please

by hopkeno

ynab_list_payees

Read-only

List YNAB payees—merchants, people, and transfer targets—to find the payee_id values needed for transactions or other budget actions.

Instructions

List payees (merchants, people, transfer targets). Use this to find payee_id values.

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": "ynab_list_payees"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return.
offsetNoRows to skip (use next_offset from a prior call).
plan_idNoPlan (budget) id from ynab_list_plans. Omit to use the configured default plan.
name_containsNoOnly payees whose name contains this text.
include_transfersNoInclude 'Transfer : <account>' payees.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds no behavioral context of its own beyond noting there is a payee_id to extract — nothing about pagination, default-plan fallback when plan_id is omitted, or result ordering. With annotations carrying the burden, this is adequate but thin.

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?

Two short sentences, the resource definition front-loaded and the actionable purpose second. Nothing is wasted and the agent gets the key fact in the first clause.

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

Completeness4/5

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

An output schema exists, so return values need not be explained, and the five optional parameters are fully documented in the schema. What remains unstated is the default-plan fallback behavior and pagination workflow (next_offset), which the description could have surfaced for a listing tool. It is otherwise complete for a simple read-only list.

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 100% and every parameter (limit, offset, plan_id, name_contains, include_transfers) is documented in the schema, so baseline 3 applies. The description mentions no parameter behavior at all, not even the name_contains filter or the transfer-payee toggle, so it adds nothing beyond the 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?

States a specific verb and resource ("List payees") and defines the resource in plain terms ("merchants, people, transfer targets"), which is more than the name alone conveys. It implicitly separates itself from the singular ynab_get_payee, but never names a sibling, so it stops short of a 5.

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?

"Use this to find payee_id values" gives a concrete triggering condition that tells an agent when this list tool is the right pick rather than a get-by-id call. There is no explicit when-not guidance or named alternative, but the context is unambiguous.

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