Skip to main content
Glama
tallyprime-mcp

tallyprime-mcp

by rkparupudi

get_trial_balance

Retrieve ledger closing balances grouped by parent group with debit and credit totals to verify books balance, flagging unposted opening-balance differences or out-of-balance accounts.

Instructions

Trial balance built from ledger closing balances, grouped by each ledger's parent group, with debit and credit totals.

'balanced' is false when total debits and credits differ by more than one rupee, which usually points at an unposted opening-balance difference.

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": "get_trial_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does well on the output side, disclosing the grouping method and the exact rule behind 'balanced' (debits and credits differing by more than one rupee, typically an unposted opening-balance difference), but it says nothing about permissions, scoping to a company, or size/pagination of the result.

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?

Two short paragraphs, front-loaded with the core definition and followed by the caveat about the 'balanced' flag. No filler, though the leading quote and the split into a separate paragraph for a single caveat is slightly more ceremony than needed.

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?

With no output schema and no annotations, the description does cover the shape and interpretation of the result, which is the most important missing piece. It remains incomplete about the one input parameter and any scoping or permission behavior, so an agent can interpret the output but not confidently control the call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single parameter, 'company', is never mentioned in the description. With low coverage the description is expected to compensate, and it does not — an agent gets no hint about whether omitting 'company' aggregates across all companies or defaults to a primary one.

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 names the specific resource (trial balance) and states how it is constructed: ledger closing balances, grouped by each ledger's parent group, with debit and credit totals. That is enough to distinguish it from siblings like get_outstanding and get_vouchers without opening any schema, though it does not explicitly contrast itself with them.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no named alternative for related reporting needs. The explanation of the 'balanced' flag is interpretive context for the output rather than a selection cue for the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.