tally-mcp-server

create_voucher

Create balanced accounting vouchers in Tally, including Payment, Receipt, Journal, Contra, Sales, and Purchase. Provide ledger entries with debits and credits to record transactions accurately.

Instructions

Create a new accounting voucher (e.g. Payment, Receipt, Journal, Contra, Sales, Purchase) in the active Tally company. Provide the full set of ledger entries; debits and credits must balance.

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": {
      "voucherType": "<voucherType>",
      "date": "<date>",
      "entries": "<entries>"
    },
    "name": "create_voucher"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	Voucher date as YYYY-MM-DD or YYYYMMDD.
`entries`	Yes	Ledger entries for the voucher. Sum of debit amounts must equal sum of credit amounts.
`narration`	No	Optional narration/description for the voucher.
`voucherType`	Yes	Tally voucher type name, e.g. "Payment", "Receipt", "Journal", "Contra", "Sales", "Purchase".
`voucherNumber`	No	Optional voucher number; Tally auto-numbers if omitted.
`partyLedgerName`	No	Optional party ledger name, relevant for Sales/Purchase vouchers.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses an important behavioral requirement: the voucher must contain the full set of ledger entries and debits must equal credits, and it references the active company context. However, it does not describe what happens on failure, whether the operation is reversible, permission requirements, or what response the caller should expect after creation.

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?

Two concise sentences deliver the core purpose, scope, and key constraint without repetition or filler. The most decision-relevant details are front-loaded: what is created, where, and what input condition must hold.

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?

For a create-oriented tool with a fully documented schema, the description covers the essential operational context: active company, voucher types, complete entries, and the balancing rule. The main gaps are the absence of return-value behavior and failure semantics, but these are minor given the schema already defines all inputs and there is no output schema to reconcile.

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 input schema already documents all six parameters clearly, including voucherType examples, date formats, the meaning of isDebit, and the entries requirement. The description adds only the general balance constraint and active-company context, which does not materially exceed what the schema already conveys.

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 uses a specific verb ('Create') with a clear resource ('accounting voucher') and gives concrete examples (Payment, Receipt, Journal, Contra, Sales, Purchase). It also scopes the action to the active Tally company, making it unmistakably distinct from the read-only sibling tools like list_vouchers and get_ledger.

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

Usage Guidelines4/5

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

The description makes clear this is the tool for creating vouchers in the active Tally company, and the balance/full-entry requirement signals when the input is valid. It does not explicitly name alternative tools for reading or listing vouchers, but since all siblings are read-only and there are no other creation tools, the usage context is effectively clear.

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

Deploy Server