Skip to main content
Glama
mcp-india-stack

mcp-india-stack

calculate_advance_tax

Read-onlyIdempotent

Calculate quarterly advance tax installments with due dates and amounts, including TDS adjustments, to plan payments and avoid interest penalties under Sections 234B and 234C.

Instructions

Calculate quarterly advance tax installment schedule per Sections 234B and 234C.

Use when planning quarterly tax payments to avoid interest penalties. Provides due dates and amounts for each installment.

Args: estimated_income: Estimated annual income for FY2025-26. regime: Tax regime for calculation. taxpayer_type: Category for slab selection. existing_tds: TDS already likely to be deducted.

Returns: Standard envelope with quarterly breakdown and interest rules.

Notes: Due dates: June 15 (15%), Sept 15 (45%), Dec 15 (75%), Mar 15 (100%). Interest 1% per month for delay under Section 234C.

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": {
      "estimated_income": "<estimated_income>"
    },
    "name": "calculate_advance_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
regimeNo'new' or 'old' tax regimenew
existing_tdsNoTDS already deducted or to be deducted in rupees
taxpayer_typeNo'individual', 'senior_citizen', or 'super_senior_citizen'individual
financial_yearNoFinancial year (e.g. '2025-26', '2026-27')2025-26
estimated_incomeYesEstimated total income for FY in rupees

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • addedInput schema / properties / financial_year
      Added value: +{
      +  "default": "2025-26",
      +  "description": "Financial year (e.g. '2025-26', '2026-27')",
      +  "title": "Financial Year",
      +  "type": "string"
      +}
  2. Changed7 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / estimated_income / title
      Added value: +"Estimated Income"
    • addedInput schema / properties / existing_tds / title
      Added value: +"Existing Tds"
    • addedInput schema / properties / regime / title
      Added value: +"Regime"
    • addedInput schema / properties / taxpayer_type / title
      Added value: +"Taxpayer Type"
    • addedInput schema / title
      Added value: +"calculate_advance_taxArguments"
    • addedOutput schema / title
      Added value: +"calculate_advance_taxDictOutput"
  3. First observedv0.3.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description goes beyond that by disclosing the actual statutory mechanics (15%/45%/75%/100% cumulative thresholds on June 15, Sept 15, Dec 15, Mar 15, and 1% monthly interest under 234C), which is real behavioral value for a purely computational tool.

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 purpose sentence is front-loaded and the structured Args/Returns/Notes layout is easy to scan. There is minor redundancy in stating 'provides due dates and amounts for each installment' and then repeating the due dates in Notes, but no sentence is fully wasted.

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?

An output schema exists, so the description does not need to enumerate return fields, and the annotated read-only/idempotent profile is already disclosed. Remaining gap is small: no note on whether the schedule accounts for already-paid installments or how 234B (non-payment) differs from the 234C (deferment) interest it details.

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%, so parameter meaning is already well documented and the description only restates the fields. It also omits the financial_year parameter entirely and pins estimated_income to 'FY2025-26' while the schema allows other years, a slight inconsistency. Baseline 3 is appropriate given the schema does the heavy lifting.

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?

States a specific verb and resource: 'Calculate quarterly advance tax installment schedule per Sections 234B and 234C.' This is clearly distinguishable from nearby siblings such as calculate_income_tax, calculate_tds, and calculate_income_tax_interest, which compute different obligations rather than the installment schedule.

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

Usage Guidelines4/5

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

'Use when planning quarterly tax payments to avoid interest penalties' gives a concrete triggering context, and the due-date/percentage notes reinforce the quarterly planning use case. However, it never contrasts itself with calculate_income_tax or calculate_income_tax_interest, so an agent comparing overlapping tax tools gets no explicit routing rule.

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