Skip to main content
Glama

Trial balance

accounting_trial_balance
Read-onlyIdempotent

Trial balance as at a date: every account's debit or credit balance and whether the ledger balances. 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_trial_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_atNoYYYY-MM-DD (default today)
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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the 'Read-only' sentence is redundant. The description does add genuine context annotations cannot carry: the GetAccountED sign-in requirement and the first-time sign-in prompt, which affects how an agent should sequence the call.

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?

Three short sentences, front-loaded with what the tool returns, then the read-only nature, then the auth prerequisite. No filler and nothing repeated that the caller would not need.

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?

With no output schema, the description usefully describes the return shape (per-account debit/credit balances and a balanced/unbalanced indicator). For a two-optional-parameter read tool with full annotation coverage, that plus the auth note is close to complete; only the default-date and empty-result behavior are unstated.

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 coverage is 100%, so both as_at (YYYY-MM-DD, default today) and business_id (practices-only client selection) are fully documented in the schema. The description only echoes the date framing and says nothing about business_id or the default behavior, so baseline 3 applies.

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?

States the specific resource (trial balance as at a date) and its outputs: every account's debit or credit balance plus whether the ledger balances. That distinguishes it from balance_sheet and general_ledger by content, though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

Implies usage through 'as at a date' and the practice/client framing, and gives the sign-in prerequisite. It does not say when to pick this over accounting_balance_sheet, accounting_general_ledger, or accounting_overview, leaving the choice 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.