Skip to main content
Glama
tallyprime-mcp

tallyprime-mcp

by rkparupudi

list_ledgers

Retrieve ledgers with opening and closing balances from TallyPrime books, filtered by group, name, or nonzero balances, to review account positions for a selected company.

Instructions

List ledgers with opening and closing balances.

group: restrict to ledgers under this group, including sub-groups (e.g. "Sundry Debtors", "Bank Accounts", "Indirect Expenses"). name_contains: case-insensitive filter on the ledger name. nonzero_only: drop ledgers whose closing balance is zero. limit: maximum ledgers to return (largest closing balances first). company: company name; defaults to the configured or active company.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_ledgers"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupNo
limitNo
companyNo
nonzero_onlyNo
name_containsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that results include opening and closing balances, that limit returns largest closing balances first, that group includes sub-groups, and that company defaults to the configured or active company. However, it does not explicitly state read-only behavior, permission scoping, or pagination/truncation behavior beyond the limit.

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?

The description is front-loaded with the core purpose and then uses compact parameter notes. Every line adds useful meaning, especially given the schema has no parameter descriptions.

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 five-parameter list tool with no annotations and no output schema, the description covers purpose, all parameter semantics, ordering, and defaults. It is not fully complete because it omits explicit alternative-tool routing and detailed return shape or permission behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 for all five parameters. It does so effectively: group semantics include sub-groups and examples, name_contains is case-insensitive, nonzero_only drops zero closing balances, limit controls count and ordering, and company defaults to the configured or active company.

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?

The description states a clear verb and resource: list ledgers, including opening and closing balances. It is specific enough to understand the tool, but it does not explicitly distinguish it from siblings such as get_trial_balance or get_outstanding.

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

Usage Guidelines2/5

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

The definition gives parameter meanings but no explicit guidance on when to use this tool instead of alternatives like get_trial_balance or get_outstanding. There are also no exclusions or prerequisite conditions beyond the company default.

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