Skip to main content
Glama
tallyprime-mcp

tallyprime-mcp

by rkparupudi

get_vouchers

Fetch vouchers (transactions) from TallyPrime within an inclusive date range, oldest first. Filter by voucher type or party name to answer book-keeping questions.

Instructions

Fetch vouchers (transactions) in a date range, oldest first.

from_date / to_date: inclusive, YYYY-MM-DD. voucher_type: e.g. "Sales", "Purchase", "Receipt", "Payment", "Journal". party_contains: case-insensitive filter on the party ledger name. limit: maximum vouchers to return. Totals by type always cover the full matching set, so narrow the range or filters if results are truncated.

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": {
      "from_date": "<from_date>",
      "to_date": "<to_date>"
    },
    "name": "get_vouchers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
companyNo
to_dateYes
from_dateYes
voucher_typeNo
party_containsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does meaningful work: it discloses result ordering (oldest first), date inclusivity, and the important non-obvious behavior that totals by type cover the full matching set even when the returned list is truncated. It does not address permissions/auth or how pagination beyond limit should be handled, which keeps it out of 5 territory.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The leading sentence states the operation and ordering, then parameters are listed one per line in a scannable format with no filler. The truncation caveat is slightly run-on across lines but every sentence carries information an agent needs.

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 6-parameter read tool with no annotations and no output schema, the definition covers filtering, ordering, date format, and truncation/totals semantics, which is most of what an agent needs to call it correctly. The gaps are the undocumented company filter and an implicit-only indication of what a returned voucher looks like.

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 0%, so the description must compensate and largely does: it defines from_date/to_date as inclusive with a YYYY-MM-DD format, gives concrete voucher_type examples, and specifies party_contains as case-insensitive on the party ledger name. The company parameter and the default limit of 200 are left undocumented, so coverage is strong but incomplete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Fetch vouchers (transactions)") plus ordering ("oldest first"), which is enough to distinguish it from the report-oriented siblings like get_trial_balance or get_outstanding. It stops short of naming when this raw-voucher listing is preferred over those aggregate views, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

The closing note ("narrow the range or filters if results are truncated") gives real guidance on how to react to a truncated result, and the filter params imply typical narrowing. There is no explicit statement of when to use this versus the sibling reporting tools, so usage is implied rather than stated.

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