Skip to main content
Glama
rehan1020

mcp-india-stack

by rehan1020

calculate_income_tax

Read-onlyIdempotent

Compute Indian income tax liability for FY2025-26 under old, new, or both tax regimes. Includes slab rates, Section 87A rebate, surcharge, and health cess.

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.

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Beyond annotations (readOnlyHint, idempotentHint), description details computational components: slab, rebate, surcharge, cess. No contradictions.

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 with front-loaded purpose and no wasted words. Highly efficient.

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?

Covers key computation aspects. With output schema present, return value details are unnecessary. Minor gap: no mention of input validation or edge cases.

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?

Input schema has 100% coverage with clear descriptions. Description adds no additional parameter insights beyond listing computation elements.

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?

Description clearly states 'Calculate Indian income tax for FY2025-26', specifying verb and resource. It distinguishes from sibling tools like calculate_advance_tax and calculate_capital_gains.

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?

Provides explicit guidance: 'Use when computing tax liability, comparing regimes, or planning deductions.' Could be improved by stating when not to use (e.g., for other tax types).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rehan1020/MCP-India-Stack'

If you have feedback or need assistance with the MCP directory API, please join our Discord server