Skip to main content
Glama
Sign In
avenir-mcp

avenir-mcp

by mathbeal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List accounts

list_accounts
Read-onlyIdempotent

Retrieve a plan's accounts with balances, bank link status, and last reconciliation date to spot broken bank links or accounts overdue for reconciliation.

Instructions

List the plan's accounts with their balances, bank link and last reconciliation.

Use it to tell the user when a bank link is broken (no transaction comes in until they fix it in YNAB) or when an account has not been reconciled for months. Its ids are the account_ids other tools take. Balances are in currency units, today's: cleared_balance is the part the bank has shown. Comparing an account with the bank is done in YNAB itself. For the balances of the months before use get_net_worth_trend; for the months ahead, forecast_balance. With several plans, pass the plan id from list_plans: 'last-used' follows the plan last opened in YNAB. Every account comes in one response, closed ones included, in one YNAB request; changes nothing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "plan_id": "<plan_id>"
    },
    "name": "list_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesYNAB plan id or 'last-used'.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, and the description adds real behavioral context beyond them: all accounts including closed ones come back in a single response/one YNAB request (no pagination), balances are today's and not historical, and cleared_balance is defined as the bank-confirmed portion. 'Changes nothing' merely restates readOnlyHint, a minor redundancy rather than added value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence front-loads purpose and return fields, and the usage/routing guidance follows logically. It runs slightly long with a few near-redundant clauses ('changes nothing', repeating the YNAB-settings disclaimer), but nearly every sentence carries decision-relevant information.

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?

Single-parameter read tool with an output schema, so return values need no prose, yet the description still clarifies balance semantics, closed-account inclusion and single-request completeness. Nothing an agent needs to select or call it correctly is missing.

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

Parameters4/5

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

With 100% schema coverage the baseline is 3, but the description adds meaning the schema lacks: where plan ids come from (list_plans) and what 'last-used' actually resolves to — the plan last opened in YNAB — plus the multi-plan condition that makes it necessary.

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?

States a specific verb and resource ('List the plan's accounts') plus the fields returned (balances, bank link, last reconciliation), which is exactly what distinguishes it from sibling listers like list_plans and list_payees. It further names get_net_worth_trend and forecast_balance as the tools for other time ranges, so an agent can route without opening schemas.

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

Usage Guidelines5/5

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

Gives concrete when-to-use triggers (broken bank link, account unreconciled for months), explicit alternatives for the wrong time horizon ('for the months before use get_net_worth_trend; for the months ahead, forecast_balance'), and an explicit out-of-scope note that comparing against the bank happens in YNAB itself.

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

Deploy Server

Other Tools