Skip to main content
Glama
mcp-india-stack

mcp-india-stack

calculate_income_tax

Read-onlyIdempotent

Calculate Indian income tax for FY2025-26 under old, new, or both regimes, compare tax liability, and estimate deductions, rebate, surcharge, cess, and take-home pay.

Instructions

Calculate Indian income tax for FY2025-26 under old, new, or both regimes.

Use when computing tax liability, comparing regimes, or planning deductions. Includes slab computation, Section 87A rebate, surcharge with marginal relief, and health & education cess.

Args: gross_income: Annual gross income in rupees. regime: 'new', 'old', or 'both' for side-by-side comparison. taxpayer_type: Category for slab selection. deduction_80c: Old regime only — Section 80C amount. deduction_80d_self: Old regime only — medical insurance self. deduction_80d_parents: Old regime only — medical insurance parents. deduction_80d_senior_parents: Old regime only — senior parent flag. deduction_80ccd_nps: Old regime only — NPS additional. deduction_24b: Old regime only — home loan interest. other_deductions: Old regime only — other amounts.

Returns: Standard envelope with per-regime breakdown, effective rate, monthly tax, take-home, and regime recommendation when both requested.

Notes: FY2025-26 rates. Estimate only — consult a CA for filing.

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": {
      "gross_income": "<gross_income>"
    },
    "name": "calculate_income_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
regimeNoTax regime: 'new', 'old', or 'both' for comparisonboth
gross_incomeYesAnnual gross income in rupees. Example: 1500000
deduction_24bNoHome loan interest under Section 24(b), capped at 2L
deduction_80cNoSection 80C deduction (PF, ELSS, LIC), capped at 1.5L
taxpayer_typeNo'individual', 'senior_citizen', or 'super_senior_citizen'individual
financial_yearNoFinancial year (e.g. '2025-26', '2026-27')2025-26
other_deductionsNoOther deductions (no cap)
deduction_80d_selfNoSection 80D medical insurance self, capped at 25K
deduction_80ccd_npsNoAdditional NPS deduction under 80CCD(1B), capped at 50K
deduction_80d_parentsNoSection 80D medical insurance parents, capped at 25K/50K
deduction_80d_senior_parentsNoIf True, parents 80D cap is 50K instead of 25K

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. Changed13 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / deduction_24b / title
      Added value: +"Deduction 24B"
    • addedInput schema / properties / deduction_80c / title
      Added value: +"Deduction 80C"
    • addedInput schema / properties / deduction_80ccd_nps / title
      Added value: +"Deduction 80Ccd Nps"
    • addedInput schema / properties / deduction_80d_parents / title
      Added value: +"Deduction 80D Parents"
    • addedInput schema / properties / deduction_80d_self / title
      Added value: +"Deduction 80D Self"
    • addedInput schema / properties / deduction_80d_senior_parents / title
      Added value: +"Deduction 80D Senior Parents"
    • addedInput schema / properties / gross_income / title
      Added value: +"Gross Income"
    • addedInput schema / properties / other_deductions / title
      Added value: +"Other Deductions"
    • addedInput schema / properties / regime / title
      Added value: +"Regime"
    • addedInput schema / properties / taxpayer_type / title
      Added value: +"Taxpayer Type"
    • addedInput schema / title
      Added value: +"calculate_income_taxArguments"
    • addedOutput schema / title
      Added value: +"calculate_income_taxDictOutput"
  3. First observedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), yet the description still adds real substance: the exact components computed (slabs, 87A rebate, surcharge with marginal relief, cess) and a caveat that results are estimates, not filing-grade. Minor internal inconsistency: the header pins the tool to FY2025-26 while the schema accepts other years, which is not disclosed.

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?

Front-loaded purpose sentence, then usage, then a clearly labelled Args/Returns/Notes structure. The Args list largely mirrors the schema, but it is terse and every line carries a regime or scope qualifier that earns its place.

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 an 11-parameter financial calculator with an output schema and full annotation coverage, the description covers purpose, computation method, optional-parameter regime rules, and a disclaimer. The one real gap is that it never mentions the financial_year parameter or explains that the tool supports years beyond 2025-26.

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 coverage is 100%, so the baseline would be 3, but the description adds genuinely new semantics the schema does not: that 80C, 80D, 80CCD, 24(b) and other_deductions apply to the old regime only. That regime-scoping is decision-relevant and absent from the schema property descriptions.

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 Indian income tax), scopes it to FY2025-26, and explicitly names the three regime modes including side-by-side comparison. An agent can distinguish this from calculate_tds, calculate_advance_tax, or calculate_surcharge without opening the schema.

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?

Gives three concrete use cases: computing liability, comparing regimes, and planning deductions. It stops short of stating when NOT to use it or naming the sibling calculators (calculate_tds, calculate_hra_exemption, calculate_presumptive_tax) that cover adjacent liability scenarios, so routing between them is still left to inference.

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