Skip to main content
Glama
Sign In
MarketingBNG

tally-mcp

by MarketingBNG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

tally_create_ledger

Create a new TallyPrime ledger under an existing group; previews changes and returns a confirm token before any write, rejecting duplicate names or missing groups.

Instructions

Create a NEW ledger in TallyPrime under an existing group.

WHEN TO USE: the user wants a new account — a customer, supplier, bank, expense head, provision and so on.

REFUSES: a name that already exists (TallyPrime would otherwise silently overwrite that ledger), and a group that does not exist.

Opening balance: give a positive amount and the side (Dr/Cr). It applies from the start of the books; leaving it out means nil.

WRITES TO TALLYPRIME, in two steps. This call only PREVIEWS: it checks the change against the live books and returns exactly what would be written plus a confirmToken — nothing is changed. Show the preview to the user, and only after they approve it call tally_confirm_write with the token. Never confirm on your own initiative, and never confirm a preview the user has not seen.

Input Schema

NameRequiredDescriptionDefault
nameYesThe new ledger name, exactly as it should appear.
emailNo
groupYesExisting group to file it under, e.g. "Sundry Debtors".
gstinNoGST registration number of the party.
stateNo
addressNoAddress lines, in order.
companyNoCompany name. Omit to use whichever company TallyPrime has loaded. If given and it is not the loaded one, the call fails with TALLY_COMPANY_NOT_LOADED rather than returning another company's data.
countryNo
pincodeNoPostal / ZIP code.
mailingNameNoName for letters and statements.
openingSideNoRequired with openingBalance.
isBillWiseOnNoMaintain balances bill-by-bill. Usually true for customers and suppliers.
openingBalanceNoPositive amount, e.g. "12500.00". Use the side field for debit or credit, never a minus sign.
incomeTaxNumberNoPAN (India) or other income-tax number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: it discloses two refusal cases (duplicate name that would otherwise be silently overwritten, nonexistent group), the opening-balance semantics, and a full two-step preview/confirm token workflow. The annotations only supply generic flags; the description supplies the operational contract.

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?

Front-loaded with the one-line purpose, then clearly labelled WHEN TO USE, REFUSES, and WRITES blocks, each carrying distinct information. Length is justified by the number of behaviors it must communicate and no sentence is filler.

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

Completeness5/5

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

For a 14-parameter mutation tool with no output schema and only a general set of annotations, this covers the gaps an agent actually needs: preconditions, refusal modes, balance semantics, the confirm handshake, and what the call returns (a preview and a confirmToken).

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 high (79%), so the baseline is 3, but the description adds real meaning for openingBalance/openingSide (positive amount plus explicit Dr/Cr side, never a minus sign, nil if omitted) that resolves an ambiguity the schema alone leaves. The other 12 parameters get no added explanation.

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?

States a specific verb and resource ("Create a NEW ledger in TallyPrime under an existing group") and immediately scopes it with concrete examples (customer, supplier, bank, expense head). The word NEW plus the group constraint distinguishes it from siblings like tally_alter_ledger or tally_create_master without opening either schema.

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?

Gives an explicit WHEN TO USE trigger and names the follow-on tool (tally_confirm_write) with the condition that selects it and a hard rule against auto-confirming. It does not explicitly say when to prefer tally_alter_ledger or tally_create_master instead, so the alternative-routing is incomplete.

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

Deploy Server

Other Tools