Skip to main content
Glama
Sign In
tally-mcp-server

tally-mcp-server

by visheshStallion
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_balance_sheet

Retrieve the balance sheet for the active company as of a specified date to assess financial position.

Instructions

Fetch the Balance Sheet report for the active company as of a given date.

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": "get_balance_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfDateNoReporting date as YYYY-MM-DD or YYYYMMDD. Defaults to Tally's current period.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. 'Fetch' and 'report' imply a read-only operation, and 'active company' plus 'as of a given date' provide useful scoping. However, it does not disclose auth requirements, error behavior, or whether some report sections are excluded.

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?

A single, front-loaded sentence with no filler. Every phrase adds relevant information: the action, the resource, the scope, and the reporting date.

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

Completeness3/5

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

Adequate for a simple one-parameter report fetch, but with no annotations and no output schema, the description could clarify the read-only nature or briefly mention that the date defaults to the current period. The sibling report tools are close enough that a small usage hint would improve completeness.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with asOfDate fully documented including its default. The description only paraphrases the date concept and adds no new constraints, aliases, or formatting details beyond the schema.

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 specific verb ('Fetch') and a specific resource ('Balance Sheet report'), and adds scope ('active company', 'as of a given date'). It is clearly distinguishable from siblings by report type, though it does not explicitly name or differentiate from get_profit_and_loss or get_trial_balance.

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?

No guidance is given on when to choose this tool over related report tools like get_trial_balance or get_profit_and_loss. There are no exclusions, preconditions, or alternative tool references, so the agent must infer usage solely from the report name.

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