Skip to main content
Glama

BRAINIAC Accounting Schedules & Close

Intercompany balance elimination

accounting-schedules_intercompany-eliminate
Read-onlyIdempotent

Pair entity/counterparty intercompany balances, flag differences above tolerance, and propose elimination entries for matched amounts. Price $0.03 USDC. POST /api/v1/accounting-schedules/intercompany-eliminate. 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": {
      "balances": "<balances>"
    },
    "name": "accounting-schedules_intercompany-eliminate"
  }
}

Input Schema

NameRequiredDescriptionDefault
balancesYesbalances, array. Required.
toleranceNotolerance, integer, from 0 to 9007199254740991. Required.

Output Schema

NameRequiredDescriptionDefault
pairsNopairs. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.
eliminationsNoeliminations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 no destruction, and the description is consistent with that: it 'proposes' entries rather than posting them, so nothing is contradicted. It adds real behavioral context beyond the annotations — output is limited to flagged differences and proposed entries, and an unpaid call returns x402 payment terms without running. It stops short of saying what happens to unmatched balances or how proposals are keyed.

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 tight sentences: the operation first, then price, then endpoint, then the payment-failure behavior. Nothing is repeated and nothing is padding; the most decision-relevant facts are front-loaded.

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, full param coverage, and rich annotations, the description only needs to cover operation semantics and the payment gate, which it does. The one residual gap is that pairing/matching logic (what counts as a pair, what happens to unmatched balances) is left implicit.

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 entity, counterparty, account, amount, currency and tolerance are already documented field-by-field. The description adds only high-level meaning — 'tolerance' as the threshold for flagging differences, 'matched amounts' as what gets eliminated. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

Uses a specific verb chain and resource: 'Pair entity/counterparty intercompany balances, flag differences above tolerance, and propose elimination entries for matched amounts.' That is far more informative than a tautology. It does not, however, position itself against any of the accounting-schedules siblings (e.g. bank-reconciliation-match, trial-balance-validate), so the agent gets no explicit sibling differentiation.

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 mention of entity/counterparty pairing and a tolerance threshold implies the domain where this applies, and the x402 payment note tells the agent a call may not execute. But there is no explicit when-to-use statement, no prerequisites (e.g. balances must be posted or in a close period), and no guidance on when a sibling schedule tool would be preferred.

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