Skip to main content
Glama
mcp-india-stack

mcp-india-stack

calculate_capital_gains

Read-onlyIdempotent

Compute capital gains tax on equity, mutual funds, real estate, gold, and other assets with STCG/LTCG breakdowns, rates, and liability for FY2025-26.

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%.

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": {
      "sale_price": "<sale_price>",
      "purchase_price": "<purchase_price>"
    },
    "name": "calculate_capital_gains"
  }
}

Input Schema

NameRequiredDescriptionDefault
asset_typeNoAsset type: equity, mutual_fund, real_estate, gold, debentures, cryptoequity
sale_priceYesSale proceeds in rupees
improvementsNoCost of improvements (for real estate)
financial_yearNoFinancial year (e.g. '2025-26', '2026-27')2025-26
purchase_priceYesOriginal purchase price in rupees
expenses_on_saleNoBrokerage, registration and other expenses on sale
holding_period_daysNoNumber of days held before sale
inflation_index_saleNoCII for sale year (for indexation)
inflation_index_purchaseNoCII for purchase year (for indexation)

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. Changed11 schema fields changedv0.5.0
    • 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"
  3. First observedv0.3.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered. The description adds genuinely useful domain behavior beyond that: the STCG 20% / LTCG 12.5% / 100K threshold rates and the 20% rule for real estate without indexation, plus the general shape of the return envelope, all of which affect how an agent should interpret results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and usage sentences are front-loaded and earn their place, as does the Notes section on tax rates. However, the Args block largely duplicates the 100%-covered schema and adds one potentially confusing gloss, so a meaningful portion of the text does not add value.

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 a nine-parameter domain calculator with an output schema and rich annotations, the description covers purpose, tax-year framing, key rate assumptions and return shape. The main residual gap is that it does not clarify when indexation parameters should be supplied versus omitted, which matters for the LTCG computation.

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 coverage is 100%, so the baseline is 3. The Args list mostly restates schema text, and the gloss 'sale_price: Sale proceeds after expenses' is slightly at odds with the separate expenses_on_sale parameter, which could mislead an agent about whether to net expenses twice. It also omits the financial_year parameter that the schema exposes.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ('Calculate capital gains tax') and scopes it to asset types and a financial year, which distinguishes it from the surrounding validation and generic tax calculators. It stops short of explicitly differentiating from the sibling calculate_income_tax, which an agent might plausibly confuse it with when computing overall tax liability.

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 computing tax liability on sale of equity, mutual funds, real estate, gold, or other capital assets' gives a clear triggering condition with concrete examples. It offers no exclusions or routing advice toward alternatives such as calculate_income_tax, so the guidance is clear but not complete.

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