Skip to main content
Glama
Sign In
MarketingBNG

tally-mcp

by MarketingBNG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

tally_alter_master

Destructive

Modify existing TallyPrime masters (groups, cost centres, stock items, etc.) by renaming, moving under a new parent, or updating fields. Preview changes before confirming.

Instructions

Change an EXISTING group, cost centre, unit, stock group, godown, stock item, voucher type or budget in TallyPrime: rename it, move it under another parent, or update the fields its kind takes (see tally_create_master). Only the fields you give change. Units cannot be renamed. For ledgers use tally_alter_ledger.

Moving a group moves every ledger under it to the new place in the balance sheet or P&L.

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
kindYesgroup, costCentre, unit, stockGroup, godown, stockItem, voucherType or budget. (Ledgers have their own tools.)
nameYesThe master to change, by its current name.
parentNogroup: parent group (required). costCentre: parent cost centre. stockGroup: parent stock group. godown: parent godown. stockItem: its stock group. voucherType: the type it is based on, e.g. "Sales" or "Journal" (required). budget: parent budget. Empty for top level.
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.
newNameNoRename it to this.
categoryNocostCentre only: its cost category.
baseUnitsNostockItem only: unit symbol, e.g. "kg". Required on create.
formalNameNounit only: full name, e.g. "Kilograms".
openingRateNostockItem only: opening rate per base unit.
decimalPlacesNounit only: decimal places for quantities.
numberingMethodNovoucherType only: number vouchers automatically or by hand.
openingQuantityNostockItem only: opening quantity in its base unit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, but the description adds substantial context the annotations cannot: the two-step preview/confirm flow, the returned confirmToken, the guarantee that the preview changes nothing, the cascading effect that moving a group moves every ledger beneath it, and the instruction never to auto-confirm. This is exactly the kind of extra behavioral detail that earns full marks.

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?

Three tight paragraphs: scope and operations first, side effects second, the write protocol last. The repetition of 'never confirm' is deliberate safety emphasis rather than padding, and every sentence carries information the agent needs.

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 12-parameter mutation tool with no output schema, the description covers the essentials: what kinds are valid, that updates are partial, per-kind constraints, company-scoping behavior is handled in schema, and the return value (preview plus confirmToken) is explained. Nothing needed to call it safely is missing.

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 100%, so the baseline is 3, but the description adds real semantics beyond the schema: 'Only the fields you give change' establishes partial-update behavior and 'Units cannot be renamed' is a constraint absent from the newName field definition. It does not add much per-kind parameter detail beyond that, so it stops short of 5.

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 (change/alter) plus the exact set of master kinds it covers, and enumerates the three operations (rename, re-parent, update fields). It explicitly routes ledgers elsewhere and points to tally_create_master for field definitions, so an agent can separate it from tally_alter_ledger, tally_create_master and tally_delete_master without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use and when-not-to-use guidance: 'For ledgers use tally_alter_ledger', 'Units cannot be renamed', 'Only the fields you give change', and the full preview-then-confirm protocol naming tally_confirm_write. Nothing about selecting this tool versus its siblings is left to inference.

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