mcp-india-stack

Overview Schema Source Related Servers Discussions Admin

calculate_income_tax

Read-onlyIdempotent

Calculate Indian income tax for FY 2025-26 under old, new, or both regimes, including slabs, rebate, surcharge, and cess, to compare monthly tax 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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`regime`	No	Tax regime: 'new', 'old', or 'both' for comparison	both
`gross_income`	Yes	Annual gross income in rupees. Example: 1500000
`deduction_24b`	No	Home loan interest under Section 24(b), capped at 2L
`deduction_80c`	No	Section 80C deduction (PF, ELSS, LIC), capped at 1.5L
`taxpayer_type`	No	'individual', 'senior_citizen', or 'super_senior_citizen'	individual
`other_deductions`	No	Other deductions (no cap)
`deduction_80d_self`	No	Section 80D medical insurance self, capped at 25K
`deduction_80ccd_nps`	No	Additional NPS deduction under 80CCD(1B), capped at 50K
`deduction_80d_parents`	No	Section 80D medical insurance parents, capped at 25K/50K
`deduction_80d_senior_parents`	No	If True, parents 80D cap is 50K instead of 25K

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedv0.5.0Aug 25, 2026
- 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"
```
First observedv0.3.0May 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Despite having readOnlyHint and idempotentHint annotations, the description adds substantial behavioral detail: slabs, rebate, surcharge, marginal relief, cess, and estimated nature of the result. It also describes the return content, including effective rate, monthly tax, take-home, and regime recommendation. The 'estimate only' caveat is useful for expectancy-setting.

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 description is slightly longer than necessary because it duplicates the schema's parameter details, but the structure is excellent: purpose first, usage next, algorithm scope, then Args/Returns/Notes. The front-loaded first sentence summarises the tool in one line, and the rest is organized so an agent can skim.

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

Completeness5/5

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

Given there is a full input schema, output schema, and read-only annotations, this description fills the remaining gaps: FY20-26 rate applicability, what calculations are included, what the return envelope contains, and the estimate/caveat. It covers everything needed to decide when to invoke this tool and what result to expect.

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 description coverage is 100%, so the schema already explains every param, but the description adds 'old regime only' qualifiers on the deduction no-param title is already clear. The Args block restates some schema text, yet it also clarifies grouping, which helps an agent avoid using these deductions with the new regime.

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 opens with the exact verb and resource: 'Calculate Indian income tax for FY2025-26 under old, new, or both regimes.' It quickly distinguishes this from tax-adjacent siblings like calculate_tds or calculate_surcharge by emphasizing income tax and regime comparison. The added 'slab computation, §87A rebate, surcharge with marginal relief, and health & education cess' makes the scope unmistakable.

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?

The description explicitly states 'Use when computing tax liability, comparing regimes, or planning deductions.' It does not name alternatives or give negative guidance, but the 'Use when' clause gives clear context for callers. The old-regime-only notes on deductions additionally guide when certain parameters should be passed.

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

Deploy Server