Skip to main content
Glama
MarketingBNG

tally-mcp

by MarketingBNG

tally_make_workpaper

Run an audit procedure or capture a TallyPrime report and render it as a Markdown workpaper for the audit file. Re-fetches data from TallyPrime so every figure comes from the books.

Instructions

Run one audit procedure and render it as a workpaper: a Markdown document carrying the objective, the population, the method and its parameters, the results, the limitations, and the exact call that reproduces it.

TWO KINDS OF PAPER, and the document says which it is:

  • test — an audit PROCEDURE this server performed over the voucher population (same values as tally_test_vouchers). The paper states the population, what was excluded and why, and the parameters applied.

  • report — one of TALLYPRIME'S OWN report views, recorded as Tally produced it (same values as tally_get_report). There is no population and nothing was selected or tested: the rule deciding what appears on it is TallyPrime's. The paper says so in its own header, because a report printout filed as though it were a performed procedure overstates the work done. Give exactly one of the two. Supplying both, or neither, is refused rather than defaulted.

WHEN TO USE: when the output has to go into an audit file rather than just answer a question in conversation. Use tally_test_vouchers to explore; use this once you know which procedure you are documenting.

IT RE-RUNS THE PROCEDURE. It does not accept figures and format them — it queries TallyPrime again and renders what came back, so every number in the document is from the books rather than from this conversation. Do NOT paste results into it; pass the same parameters you would pass to tally_test_vouchers and let it fetch. If the figures differ from an earlier run, the books changed, and that is worth knowing.

IT DOES NOT WRITE THE CONCLUSION. Supply conclusion if you have reached one. If you do not, the document says the conclusion was not recorded, rather than inventing one — an unsigned workpaper should look unsigned. Never fill this parameter with your own inference from the results; it is the auditor's to write.

RETURNS: markdown, the rendered document, plus the structured result it was rendered from so nothing is lost. Save the markdown to the audit file.

Read-only: nothing here can modify TallyPrime.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
testNoWhich procedure to run and document. Same values as tally_test_vouchers. Give either this or `report`, not both.
partyNoRestrict to vouchers with this party.
queryNoRestrict to vouchers matching this text.
ledgerNoRestrict to vouchers against this ledger.
reportNoDocument one of TallyPrime's own report views instead of running a procedure. Same values as tally_get_report. Give either this or `test`, not both. The document is rendered differently and says plainly that it records a report as TallyPrime produced it, not a procedure this server performed — see the tool description.
toDateNoEnd of the period, ISO YYYY-MM-DD. Must be on or after fromDate.
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.
fromDateNoStart of the period, ISO YYYY-MM-DD. Omit both dates for the financial year containing today; the resolved range is echoed back.
maxAmountNoRestrict to vouchers at most this large.
minAmountNoRestrict to vouchers at least this large.
objectiveYesWhat this procedure was performed to establish, in your words. Required — a workpaper without a stated objective cannot be reviewed, because there is no way to judge whether the work done was the work needed.
referenceNoYour working paper reference, e.g. "C-140". Rendered in the header.
thresholdNojournal_screen only: normally your materiality figure.
conclusionNoWhat you concluded from the results. Optional, and NEVER to be filled in on the auditor's behalf: omitted renders as "not recorded", which is the honest state of a paper nobody has signed off.
cutoffDaysNocutoff only.
preparedByNoWho performed the procedure. Renders as "not recorded" when omitted.
sampleSeedNosample only: pass to reproduce.
sampleSizeNosample only.
voucherTypeNoRestrict the population to this type.
sampleMethodNo
benfordDigitsNo
relatedPartiesNo
roundMultipleOfNoWhat counts as round.
Behavior5/5

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

No annotations are provided, so the description must carry the full burden, and it does. It discloses that the tool re-runs the procedure, fetches data from TallyPrime ('It does not accept figures and format them — it queries TallyPrime again'), that it does not write the conclusion unless supplied ('Never fill this parameter with your own inference'), and that it is read-only ('nothing here can modify TallyPrime'). These behavioral traits go well beyond what a typical description would include, fully meeting transparency requirements.

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?

Despite being long, the description is tightly structured with clear sections: the two kinds of paper, when to use, re-running behavior, conclusion handling, and return value. Every sentence adds necessary operational or behavioral context not elsewhere available. It is front-loaded with the core purpose and uses bold headers for scannability, making it dense yet concise—appropriate for the complexity of the tool.

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 tool with 23 parameters, two modes, no output schema, and no annotations, the description is remarkably complete. It explains the two modes, the re-run behavior, the return format, the conclusion handling, and provides concrete guidance on what to do with the output ('Save the markdown to the audit file'). It even notes that the resolved date range is echoed back, which is a subtle behavior. Nothing essential for correct invocation 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 87%, so the schema already documents most parameters. The description adds meaningful context beyond the schema: it explains that `conclusion` is the auditor's own and must never be inferred, that `objective` is required because without it a workpaper cannot be reviewed, and it reinforces the mutual exclusivity of `test` and `report`. These enrichments justify a score above the baseline of 3, though not a 5 since the schema already covers most semantics.

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 opens with a precise statement: 'Run one audit procedure and render it as a workpaper: a Markdown document carrying the objective, the population, the method and its parameters, the results, the limitations, and the exact call that reproduces it.' This defines a specific verb, resource, and output. It also clarifies the two distinct modes (test and report) and explicitly contrasts with siblings tally_test_vouchers and tally_get_report, making the purpose unambiguous.

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?

The description contains an explicit 'WHEN TO USE' section: 'when the output has to go into an audit file rather than just answer a question in conversation. Use `tally_test_vouchers` to explore; use this once you know which procedure you are documenting.' It also instructs not to paste results but to pass the same parameters, and states that supplying both test and report is refused. This gives clear guidance on when to use this tool versus alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MarketingBNG/Tally-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server