Related Servers

Each tool targets a distinct resource and action — company details, masters, vouchers, statements, stock, banking, tax, audit procedures — and the closest pairs (get_statement vs get_report, get_vouchers vs summarise_movements, get_closing_stock vs get_masters stockItem) are explicitly cross-referenced with WHEN TO USE guidance that forecloses misselection. Tools that could plausibly overlap (get_ledger_transactions vs get_party_statement) are separated by scope: one ledger vs all ledgers matching a party. No two tools appear to do the same thing.

All 25 tools follow the identical tally_<verb>_<noun> snake_case pattern with a consistent prefixaineiston; the verbs are a small predictable set (get, list, read, search, summarise, check, calculate, test, make) and the nouns name the domain object (vouchers, statement, masters, stock). No camelCase, no mixed verb styles, no vague names like 'process' or 'helper'. The pattern is so regular that a tool's purpose is guessable from its name alone.

At 25 tools, this sits at the top of the borderline '16-25 feels heavy' band, and nearly every tool earns its place given the breadth: TallyPrime data access (masters, vouchers, statements, inventory, banking, GST, TDS, outstanding) plus a genuinely separate audit domain (tests, workpapers, materiality, confirmations, tie-out). The count is stretched by infrastructure-style tools (connection_status, the exported-books pair) and audit-specific ones that could arguably live in their own server, which keeps this from a 4.

The read-only surface is thoroughly covered: companies, masters, vouchers, ledger statements, party statements, financial statements, inventory both as summary and movement, bank reconciliation, GST, TDS, outstanding, search, plus an unusually complete audit layer (tie-out, tests, workpapers, materiality, confirmations, fixed assets). Minor gaps exist and are honestly disclosed rather than hidden — no Edit Log/audit-trail access, unverified row shapes on four report IDs, no payroll or budget-specific tools — but none create dead ends since the descriptions name the workaround.