Skip to main content
Glama

TrueCalci

by com.truecalci
OverviewDiscussionsAdmin

India advance tax instalments

advance_tax
Read-onlyIdempotent

Calculate statutory quarterly advance tax installments and interest penalties under Sections 208, 209, 211, 234B, and 234C of the Indian Income-tax Act. Determines exact installment deadlines (15% June 15, 45% Sept 15, 75% Dec 15, 100% March 15) and statutory shortfall interest.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
as_of_dateYesCivil date YYYY-MM-DD. Selects the rule pack in force on that date. Required: the engine will not assume a date.
assessed_taxYesEstimated total annual net tax liability after TDS/TCS credits in INR (₹). Advance tax mandatory if >= ₹10,000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / as_of_date
      Added value: +{
+  "description": "Civil date YYYY-MM-DD. Selects the rule pack in force on that date. Required: the engine will not assume a date.",
+  "example": "2026-09-26",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "assessed_tax"
-]New value: +[
+  "assessed_tax",
+  "as_of_date"
+]
  2. Changed3 schema fields changed
    • addedInput schema / properties / assessed_tax / example
      Added value: +"150000.00"
    • addedInput schema / properties / assessed_tax / pattern
      Added value: +"^\\d+\\.\\d{2}$"
    • changedInput schema / properties / assessed_tax / type
      Previous value: -"number"New value: +"string"
  3. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description only needs to add substantive context. It does so by disclosing the exact statutory basis (Sections 208, 209, 211, 234B, 234C), the quarterly percentages, and deadlines, making the calculation behavior predictable. No contradiction with annotations.

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?

Two sentences, front-loaded with the core verb and object, and every clause adds information: the legal sections, the quarterly percentages/deadlines, and the shortfall-interest behavior. It is compact without sacrificing specificity.

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 two-parameter, read-only calculator, the description covers the purpose, legal basis, and key outputs (deadlines and shortfall interest). The main gap is the absence of explicit output-structure details, but the schema fully documents the inputs and the behavior is simple enough to infer.

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 clear descriptions, examples, and patterns for both assessed_tax and as_of_date, so the schema carries the burden. The description does not add parameter-specific meaning beyond implying they feed the statutory calculation, which matches the baseline.

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 names a specific verb (Calculate), a precise resource (statutory quarterly advance tax installments and interest penalties), and cites the governing statutory sections. It is immediately distinguishable from sibling tax tools like tds, tcs, and indian_income_tax because it is explicitly about advance tax instalments.

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 description implies its use case: computing advance tax installments and related interest. However, it gives no explicit when-to-use/when-not-to-use guidance or alternatives, and with many sibling tax tools an agent must infer that this tool is not for TDS/TCS or general income-tax computation.

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

All TrueCalci toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources