Skip to main content
Glama

BRAINIAC Accounting Schedules & Close

Validate a trial balance

accounting-schedules_trial-balance-validate
Read-onlyIdempotent

Check debit/credit equality, abnormal balances by account type, duplicate codes and lines with both debit and credit. Price $0.02 USDC. POST /api/v1/accounting-schedules/trial-balance-validate. An unpaid call returns the x402 payment terms and does not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "accounts": "<accounts>"
    },
    "name": "accounting-schedules_trial-balance-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountsYesaccounts, array. Required.

Output Schema

NameRequiredDescriptionDefault
issuesNoissues. Array.
sourcesNosources. Array.
balancedNobalanced. Boolean.
differenceNodifference. Number.
totalDebitNototalDebit. Number.
limitationsNolimitations. Array.
totalCreditNototalCredit. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds genuinely non-redundant behavior: a $0.02 USDC charge and the fact that an unpaid call returns x402 payment terms and does not execute, which is critical for an agent to interpret a non-result response. It stops short of describing severity/failure semantics, but the output schema covers the payload.

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?

Four short sentences, front-loaded with what is validated, followed by price, endpoint, and payment-gating behavior in descending order of importance. The raw POST path is the weakest sentence for an agent that never constructs URLs itself, but it is part of the API contract and costs only one line.

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 an output schema present, the description does not need to explain return values, and it correctly spends its budget on the checks performed and the paid-call mechanics that annotations cannot express. Nothing required to invoke the tool is missing; the only gap is guidance on acting on failures versus passing results.

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?

There is a single top-level parameter whose nested properties are 100% schema-described, so the schema baseline would be 3. The description earns a bump because the listed checks map directly onto specific fields the agent must populate correctly (type drives abnormal-balance detection, code drives duplicate detection, debit/credit drive balance and both-sides checks), telling the agent which data quality matters.

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 names a concrete verb set and enumerates the exact checks performed: debit/credit equality, abnormal balances by account type, duplicate codes, and lines carrying both debit and credit. That check list is unambiguous and could not be confused with any sibling tool, which are all schedule-building/derivation tools (depreciation, amortization, FX revaluation, etc.).

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?

Usage is only implied by the nature of the tool: an agent can infer it should validate a trial balance before downstream use. There is no explicit statement of when to call this versus the schedule/statement-building siblings, no prerequisites on input completeness, and no note about whether a failing validation blocks other operations.

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.

Resources