Skip to main content
Glama
make-cents-please

make-cents-please

by hopkeno

ynab_list_accounts

Read-only

List accounts with current, cleared, and uncleared balances, and find account IDs required for other budget tools.

Instructions

List accounts with current, cleared and uncleared balances. Use this to find account_id values for other tools.

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_accounts"
  }
}

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.
on_budgetNoTrue = budget accounts only, False = tracking only.
account_typeNoFilter by type, e.g. checking, savings, creditCard, mortgage.
include_closedNoInclude closed accounts.

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 and destructiveHint=false, so the safety profile is covered; the description adds only the shape of returned balances. It says nothing about result volume, pagination caps, or default exclusion of closed accounts beyond what the schema carries.

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, front-loaded with what is returned and followed by the primary use case. No filler or repetition of the tool name.

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?

With a full output schema, complete parameter documentation, and read-only annotations, the description only needs to supply purpose and routing, which it does. Minor omission: no mention that closed accounts are excluded by default or that results are paginated, though both are visible in schema defaults.

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 coverage is 100%, so every parameter (limit, offset, plan_id, on_budget, account_type, include_closed) is already documented in the schema. The description adds no filtering or paging guidance beyond that, so the baseline 3 applies.

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 names a specific verb and resource ('List accounts') and adds what the records carry ('current, cleared and uncleared balances'). It is clearly distinct from the singular ynab_get_account by name and semantics, though it never explicitly contrasts with it.

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?

It gives a concrete when-to-use: 'Use this to find account_id values for other tools,' which is the key reason an agent would pick list over get. It does not state when to prefer ynab_get_account or when a listing is unnecessary, so no exclusion guidance.

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