Skip to main content
Glama

BRAINIAC Accounting Schedules & Close

Build income statement and balance sheet

accounting-schedules_financial-statements-build
Read-onlyIdempotent

Roll a mapped trial balance into income-statement and balance-sheet lines, add net income to equity, and check A = L + E. Price $0.03 USDC. POST /api/v1/accounting-schedules/financial-statements-build. 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_financial-statements-build"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountsYesaccounts, array. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
limitationsNolimitations. Array.
balanceSheetNobalanceSheet. Object.
incomeStatementNoincomeStatement. Object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 important behavioral context beyond annotations: the $0.03 USDC price, the POST endpoint, and the rule that an unpaid call returns x402 payment terms and does not run. It does not describe what happens if the balance check fails.

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 tight sentences that front-load the core computation and then compactly cover payment and endpoint details. Every sentence carries useful information and there is no redundant wording.

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?

An output schema exists and annotations cover the safety profile, so the description need not explain return values. It covers the main computation and payment gate, but it could say more about required input mapping assumptions or how an imbalance is surfaced, which would help an agent invoke it correctly.

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 the detailed nested account fields are already documented in the schema. The description only refers to a 'mapped trial balance' and adds no additional syntax, constraints, or examples for the accounts parameter beyond what the schema provides.

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 states a specific verb and resource: roll a mapped trial balance into income-statement and balance-sheet lines, add net income to equity, and check A = L + E. It clearly identifies both produced statements and the accounting equation check, so an agent can understand the operation without opening the schema.

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?

The description implies the tool is used when you have a mapped trial balance, but it does not explicitly say when to use this versus sibling tools such as trial-balance-validate or how to prepare the accounts array. No exclusions or alternative routing are provided.

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