Skip to main content
Glama
ninetails-io

gnucash-mcp

list_accounts

List GnuCash chart of accounts with subtree and text filters. Get paginated results and account IDs for use in transactions, budgets, and reports.

Instructions

List all accounts in the GnuCash chart of accounts.

Leads with a Showing X-Y of Z accounts line, then a compact one-line-per-account format by default. Page with offset; limit=0 returns the count only. Use verbose=true for full JSON with guid, type, commodity, etc.

To FIND an account without paging the whole chart, pass query — a case-insensitive substring matched against each account's full path and description (e.g. query="grocer" or query="4930" on a numbered chart). Results emit %short GUIDs that every account-taking tool accepts. For searching transactions by text or amount, use search_transactions.

Args: root: Filter to a subtree (e.g., "Expenses" for expense accounts only). verbose: If true, return full JSON details for each account. limit: Page size (default 50, max 250). 0 = count only. offset: 0-indexed first row to return (default 0). query: Case-insensitive substring filter on account path/description. Combines with root.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rootNo
limitNo
queryNo
offsetNo
verboseNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Despite no annotations being provided (so the description carries full burden), it discloses key behavioral traits: that it leads with a 'Showing X-Y of Z accounts' line, emits %short GUIDs that other tools accept, and that limit=0 returns count only. It lacks explicit read-only declaration, but the output-schema plus detailed behavioral description adds significant context. Minor gap: doesn't explicitly state it's a safe/read-only operation given zero annotation coverage.

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?

Well-structured with clear sections and a documented Args block. The description is moderately verbose but every sentence earns its place—paging format, query behavior, and cross-tool references are all valuable. Could be tightened slightly but the added value justifies the length.

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?

Even though an output schema exists, this tool has 5 parameters and multiple behavioral modes (paging, count-only, verbose, querying). The description thoroughly covers the return format, paging semantics, GUID output, and cross-tool guidance. Given the tool's complexity and zero annotation coverage, the description is complete and self-sufficient.

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?

Schema description coverage is 0%, so the description carries the full burden. The description thoroughly explains all 5 parameters: root (subtree filter with expenses example), verbose (full JSON), limit (default 50, max 250, 0=count), offset (0-indexed), and query (case-insensitive substring with concrete examples like query='grocer'). This compensates fully for the schema coverage gap.

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 'List all accounts in the GnuCash chart of accounts' with a specific verb+resource. It differentiates from siblings by describing the paging format, verbose mode, and query filtering. It explicitly distinguishes from search_transactions, showing good sibling differentiation.

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?

The description explicitly explains when to use this tool vs searching: 'To FIND an account without paging the whole chart, pass query' and explicitly directs transaction searching to 'search_transactions'. It also explains when to use verbose=true, providing clear context for alternative approaches.

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/ninetails-io/gnucash-mcp'

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