Skip to main content
Glama

Chart of accounts

accounting_chart_of_accounts
Read-onlyIdempotent

The business's chart of accounts (code, name, type). Use the codes when filing a bank line to an account. Read-only. Needs the user's GetAccountED sign-in (they are asked to sign in the first time).

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

Input Schema

NameRequiredDescriptionDefault
typeNoOnly this account type
business_idNoAccounting practices only: which client's books (an id from accounting_list_my_businesses). Leave out to use the books chosen at sign-in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by stating that the user must sign in with GetAccountED and will be prompted the first time, which is not captured by 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 three short sentences with no wasted wording. The core purpose is front-loaded, followed by usage context and the authentication prerequisite.

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 simple read-only lookup with two optional parameters, rich annotations, and no output schema, the description covers purpose, usage, and authentication. It could be slightly more complete by explicitly saying it returns the full chart of accounts, but the essential information is present.

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%, so both parameters are already well documented in the input schema. The description does not add parameter-specific meaning beyond the schema, so the baseline score of 3 is appropriate.

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 identifies the specific resource, the business's chart of accounts, and names the returned fields (code, name, type). It does not use an explicit retrieval verb such as 'list' or 'get', but the purpose is still clear and distinguishable from sibling accounting tools.

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 usage context: use the account codes when filing a bank line to an account, which links it to accounting_file_bank_line. It also states the sign-in prerequisite, though it does not explicitly name alternatives or 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.