Skip to main content
Glama

Trial Balance Difference

bpj_trial_balance_difference
Read-onlyIdempotent

Compare ledger debit and credit totals and identify the smaller side and its shortfall.

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": {
      "debits": "<debits>",
      "credits": "<credits>"
    },
    "name": "bpj_trial_balance_difference"
  }
}

Input Schema

NameRequiredDescriptionDefault
debitsYes
creditsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description adds that the tool reports the smaller side and the shortfall amount, which is genuine behavioral value. However, it is silent on edge behavior such as equal debits and credits (is there a 'smaller side'?), units, and rounding or precision of the shortfall.

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?

A single front-loaded sentence with no filler; the primary action ('compare') comes first and the result ('smaller side and its shortfall') follows. Nothing could be removed without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-number calculator with no output schema, the description should say enough about the returned shape that an agent can consume it; 'smaller side and shortfall' only loosely does so, leaving the tie case and exact fields unspecified. Annotations cover safety and idempotency, so the remaining gap is mainly about output form and edge conditions.

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?

Schema description coverage is 0% – the params carry only titles and numeric bounds – so the description must supply semantics, and it does: both inputs are 'totals' of debits and credits to be compared, and the derived output is the gap between them. It does not state currency/unit expectations, whether values are integers or decimals, or how the shortfall is signed, which keeps it below a top score.

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 uses a specific verb and resources: "Compare ledger debit and credit totals and identify the smaller side and its shortfall." An agent immediately knows this is a reconciliation-style computation, not a lookup. It does not name or distinguish itself from any sibling, but the sibling list contains no obvious functional alternative, so the gap is minor.

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: 'ledger' and 'trial balance' signal an accounting reconciliation context, and the two required inputs make the calling pattern obvious. There is no explicit statement of when to prefer this over a general arithmetic or balance tool, and no prerequisites or exclusions are given.

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.