mcp-india-stack

Overview Schema Source Related Servers Discussions Admin

calculate_capital_gains

Read-onlyIdempotent

Compute capital gains tax for Indian assets including equity, mutual funds, real estate, gold, and crypto. Enter sale and purchase prices to get STCG/LTCG breakdown, tax rates, and tax liability.

Instructions

Calculate capital gains tax for various asset types (FY2025-26).

Use when computing tax liability on sale of equity, mutual funds, real estate, gold, or other capital assets.

Args: sale_price: Sale proceeds after expenses. purchase_price: Original purchase price. asset_type: Type of asset sold. holding_period_days: Days held before sale. inflation_index_purchase: Cost Inflation Index for purchase year. inflation_index_sale: Cost Inflation Index for sale year. expenses_on_sale: Expenses incurred during sale. improvements: Cost of improvements (for real estate).

Returns: Standard envelope with STCG/LTCG breakdown, tax rates, and liability.

Notes: Budget 2024 rates: STCG 20% (equity/MF), LTCG 12.5% (equity/MF threshold 100K). Real estate without indexation taxed at 20%.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`asset_type`	No	Asset type: equity, mutual_fund, real_estate, gold, debentures, crypto	equity
`sale_price`	Yes	Sale proceeds in rupees
`improvements`	No	Cost of improvements (for real estate)
`purchase_price`	Yes	Original purchase price in rupees
`expenses_on_sale`	No	Brokerage, registration and other expenses on sale
`holding_period_days`	No	Number of days held before sale
`inflation_index_sale`	No	CII for sale year (for indexation)
`inflation_index_purchase`	No	CII for purchase year (for indexation)

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.5.0Aug 25, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / asset_type / title
```
Added value: +"Asset Type"
```
- addedInput schema / properties / expenses_on_sale / title
```
Added value: +"Expenses On Sale"
```
- addedInput schema / properties / holding_period_days / title
```
Added value: +"Holding Period Days"
```
- addedInput schema / properties / improvements / title
```
Added value: +"Improvements"
```
- addedInput schema / properties / inflation_index_purchase / title
```
Added value: +"Inflation Index Purchase"
```
- addedInput schema / properties / inflation_index_sale / title
```
Added value: +"Inflation Index Sale"
```
- addedInput schema / properties / purchase_price / title
```
Added value: +"Purchase Price"
```
- addedInput schema / properties / sale_price / title
```
Added value: +"Sale Price"
```
- addedInput schema / title
```
Added value: +"calculate_capital_gainsArguments"
```
- addedOutput schema / title
```
Added value: +"calculate_capital_gainsDictOutput"
```
First observedv0.3.0May 30, 2026

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 and idempotentHint=true, so the safety profile is covered. The description adds relevant behavioral context beyond annotations, including Budget 2024 rate rules, STCG/LTCG breakdown expectations, the default 365-day holding period, and the specific return envelope containing tax rates and liability.

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 well-structured with a summary sentence, Args, Returns, and Notes sections. It is somewhat longer than minimal, but the length is justified by tax context and asset-type coverage. The key usage condition is front-loaded in the opening sentence.

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?

The description covers the fiscal year, usage window, key tax regime, asset types, and output envelope, which is sufficient for a read-only calculator with an output schema. It does not exhaustively explain complex edge cases like indexation thresholds or asset-specific holding period differences, but those are partially covered by parameters and notes.

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?

The input schema already documents all 8 parameters at 100% coverage, including descriptions like 'sale proceeds in rupees' and 'CII for purchase year'. The description mostly restates the parameters and adds modest clarification such as 'sale proceeds after expenses' and 'expenses incurred during sale', but it does not materially improve on the schema's parameter documentation.

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 a specific verb and resource: 'Calculate capital gains tax for various asset types' and scopes it to FY2025-26. It names the covered asset classes (equity, mutual funds, real estate, gold), which clearly distinguishes this tool from sibling calculators like calculate_income_tax, calculate_tds, and calculate_gst.

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 gives an explicit 'Use when computing tax liability on sale of equity, mutual funds, real estate, gold, or other capital assets' condition. It does not explicitly exclude or direct to alternatives like calculate_income_tax, but the stated trigger context is clear enough for an agent to select it among the calculation siblings.

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

Deploy Server