Skip to main content
Glama
mcp-india-stack

mcp-india-stack

calculate_surcharge

Read-onlyIdempotent

Calculates income tax surcharge and marginal relief from total income and base tax, with separate new and old regime rates.

Instructions

Calculate surcharge and marginal relief for a given income and base tax.

Use when computing surcharge as a standalone calculation, separate from the full income tax tool. The income tax tool uses this logic internally.

Args: total_income: Total income in rupees. base_tax: Base tax amount before surcharge. regime: 'new' (capped at 25%) or 'old' (up to 37%).

Returns: Standard envelope with surcharge rate, before/after marginal relief, and cess base.

Notes: FY2025-26 rates. New regime surcharge capped at 25%.

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": {
      "total_income": "<total_income>",
      "base_tax": "<base_tax>",
      "regime": "<regime>"
    },
    "name": "calculate_surcharge"
  }
}

Input Schema

NameRequiredDescriptionDefault
regimeYes'new' or 'old' tax regime
base_taxYesBase tax amount before surcharge
total_incomeYesTotal income in rupees
financial_yearNoFinancial year (e.g. '2025-26', '2026-27')2025-26

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. Changed6 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / base_tax / title
      Added value: +"Base Tax"
    • addedInput schema / properties / regime / title
      Added value: +"Regime"
    • addedInput schema / properties / total_income / title
      Added value: +"Total Income"
    • addedInput schema / title
      Added value: +"calculate_surchargeArguments"
    • addedOutput schema / title
      Added value: +"calculate_surchargeDictOutput"
  3. First observedv0.3.0

TDQS

A4.5/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), and the description adds real domain context: the FY2025-26 rate basis, the 25% cap under the new regime, and the fact that the return includes surcharge rate and before/after marginal relief. The one wrinkle is that the Notes pin FY2025-26 rates while the schema accepts a financial_year of '2026-27', leaving it unclear how the year parameter interacts with the stated rates.

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 purpose and the sibling routing are front-loaded in the first two sentences, which is exactly right. The Args block, however, restates the schema descriptions nearly verbatim ("Base tax amount before surcharge", "Total income in rupees") and earns little for the space it occupies.

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?

With an output schema present, the description needn't detail return values, and the brief Returns note is sufficient. For a 4-parameter calculation tool this is nearly complete; the only gap is the unexplained financial_year parameter and its relationship to the hard-coded FY2025-26 rate note.

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 baseline is 3, but the description adds meaning the schema lacks: the regime parameter's effect (new capped at 25%, old up to 37%). It does not explain the financial_year parameter at all, which is the one place the schema could have used help.

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 surcharge and marginal relief") plus the inputs it operates on (income and base tax). It also distinguishes itself from the nearest sibling, calculate_income_tax, by noting that this is the standalone calculation the income tax tool uses internally.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use it ("when computing surcharge as a standalone calculation, separate from the full income tax tool") and names the alternative it is not. The routing decision between this and calculate_income_tax is fully answerable from the description alone.

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