Skip to main content
Glama

ynab_get_account

Read-onlyIdempotent

Retrieve detailed account information including current balance, cleared and uncleared balances, account type, and status. Provide account ID; optionally specify budget ID.

Instructions

Get details for a single account including current balance.

Args:

  • budget_id (string, optional): Budget UUID. Omit to use the default budget.

  • account_id (string, required): Account UUID.

  • response_format (string, optional): "json" or "markdown" (default: "markdown").

Returns: account (id, name, type, balance, cleared_balance, uncleared_balance, on_budget, closed), cached, cache_info

Errors:

  • "No default budget set" → run ynab_set_default_budget first

  • "Account not found" → invalid account_id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
budget_idNo
account_idYes
response_formatNomarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cachedNoIndicates if data was served from cache
cache_infoNoHuman-readable cache status message (e.g., "Cache hit", "Cache miss")
usedDeltaNoIndicates if delta merge optimization was applied for budgets
accountYesAccount details
Behavior4/5

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

Annotations already indicate read-only, non-destructive, and idempotent behavior. The description adds that the response includes 'cached' and 'cache_info', which hints at caching behavior, and also lists possible errors, providing useful behavioral context beyond the annotations.

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 well-structured with Args, Returns, and Errors sections. It is concise, every sentence adds value, and the main purpose is front-loaded.

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?

Given that an output schema exists, the description's list of return fields is sufficient. It also covers error cases and provides enough context for an agent to use this tool correctly without missing information.

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?

Schema description coverage is 0%, but the description compensates by explaining each parameter's purpose: budget_id is an optional UUID to use default budget, account_id is required, and response_format offers 'json' or 'markdown' with default. This adds significant clarity not present in the schema.

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 the verb 'Get' and the resource 'details for a single account', specifying exactly what the tool does. It distinguishes itself from siblings like 'ynab_list_accounts' by indicating it retrieves a single account.

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 provides usage context such as omitting budget_id to use the default budget, and includes error messages that guide the agent on prerequisites (e.g., setting default budget). However, it does not explicitly compare to alternatives or state when not to use this tool.

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

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/dizzlkheinz/ynab-mcpb'

If you have feedback or need assistance with the MCP directory API, please join our Discord server