Skip to main content
Glama

Get Chart Of Accounts

get_chart_of_accounts
Read-onlyIdempotent

List account categories (chart of accounts). Use when the user asks about their chart of accounts, account codes, or available categories for categorizing transactions. On a national chart an account marked takes_postings: false is a heading with analytic accounts under it: never post, categorise or journal to it, use one of its analytic accounts (the longer codes that start with its code) or add one with create_account_category.

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

Input Schema

NameRequiredDescriptionDefault
typeNoFilter by type: income, expense, asset, liability, equity, cost_of_sales
companyNoWhich company to read, by name or id, when the account has more than one (see list_companies). Leave it out to use the only company, or the default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description goes beyond the bar by disclosing a domain trap that annotations cannot express: heading accounts with takes_postings: false are structural, not postable, and analytic accounts are identified by longer codes prefixed with the heading's code. That is exactly the kind of behavioral context that prevents a downstream write error.

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?

Front-loaded with the verb and resource, then usage triggers, then the caveat. The final sentence is long and dense, but every clause carries operational consequence (never post, use analytic accounts, or create one), so it earns its length; only minor tightening is possible.

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?

For a two-optional-parameter read tool with full annotation coverage and no output schema, the definition covers purpose, invocation triggers, and the main semantic hazard. It does not describe the shape of returned entries (beyond implying a takes_postings flag), which would be a modest addition for an agent planning follow-up calls.

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 both parameters (type, company) carry enum-like value lists and guidance about multi-company selection and the list_companies fallback. The description adds no parameter-level detail beyond that, so the schema is doing the work and the baseline of 3 applies.

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 account categories (chart of accounts)') and immediately ties it to the user intents it serves ('chart of accounts, account codes, or available categories for categorizing transactions'). This is clearly distinguishable from sibling reads like get_accounts_status or get_balance.

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 explicit when-to-use triggers keyed to user phrasing, plus a hard constraint: on a national chart, an account with takes_postings: false must never receive postings, and the agent should instead use one of its analytic accounts or call create_account_category. The alternative action is named rather than left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.