TrueCalci

India income tax (new vs old regime)

tax_in

Read-onlyIdempotent

Compute Indian personal income tax for the tax year in force on as_of_date (Income-tax Act, 2025 from tax year 2026-27; the 1961 Act before), comparing the new regime (standard deduction and Section 87A rebate) with the old regime (Chapter VI-A deductions such as 80C and 80D), and naming the lower one. Pass regime to get only one.

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": {
      "gross_income": "<gross_income>",
      "as_of_date": "<as_of_date>"
    },
    "name": "tax_in"
  }
}

Input Schema

Name	Required	Description	Default
`regime`	No	Tax regime to compute: 'both' (dual comparison), 'new', or 'old'.	both
`as_of_date`	Yes	Statutory as-of date in ISO YYYY-MM-DD format.
`gross_income`	Yes	Gross annual income from all sources in INR (₹).
`deductions_80c`	No	Chapter VI-A Section 80C deductions (capped at ₹1,50,000 for Old Regime).
`deductions_80d`	No	Section 80D health insurance premium deduction for Old Regime.

Output Schema

Name	Required	Description	Default
`mode`	No
`engine`	No
`status`	No
`as_of_date`	No
`comparison`	No
`disclaimer`	No
`new_regime`	No
`old_regime`	No
`minor_units`	No
`gross_income`	No
`new_regime_tax`	No
`old_regime_tax`	No
`tax_difference`	No
`comparison_note`	No
`calculation_type`	No
`lower_tax_regime`	No
`statutory_authority`	No
`tax_difference_formatted`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 2, 2026

addedOutput schema / properties / comparison_note

Added value: +{
+  "type": [
+    "string",
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / lower_tax_regime

Added value: +{
+  "type": [
+    "string",
+    "number",
+    "null"
+  ]
+}

removedOutput schema / properties / optimal_regime

Removed value: -{
-  "type": [
-    "string",
-    "number",
-    "null"
-  ]
-}

removedOutput schema / properties / recommendation

Removed value: -{
-  "type": [
-    "string",
-    "number",
-    "null"
-  ]
-}

addedOutput schema / properties / tax_difference

Added value: +{
+  "type": [
+    "string",
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / tax_difference_formatted

Added value: +{
+  "type": [
+    "string",
+    "number",
+    "null"
+  ]
+}

removedOutput schema / properties / tax_savings

Removed value: -{
-  "type": [
-    "string",
-    "number",
-    "null"
-  ]
-}

removedOutput schema / properties / tax_savings_formatted

Removed value: -{
-  "type": [
-    "string",
-    "number",
-    "null"
-  ]
-}

Changed1 schema field changedSep 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "as_of_date": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "calculation_type": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "comparison": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "disclaimer": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "engine": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "gross_income": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "minor_units": {},
+    "mode": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "new_regime": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "new_regime_tax": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "old_regime": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "old_regime_tax": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "optimal_regime": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "recommendation": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "status": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "statutory_authority": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "tax_savings": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "tax_savings_formatted": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedSep 15, 2026

addedInput schema / properties / as_of_date

Added value: +{
+  "description": "Statutory as-of date in ISO YYYY-MM-DD format.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "gross_income"
-]New value: +[
+  "gross_income",
+  "as_of_date"
+]

AddedSep 11, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: which statute applies at a given date, what each regime models (standard deduction, 87A rebate vs Chapter VI-A), and that the lower liability is reported.

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 tight sentences, front-loaded with the core action, then the date/statute rule, then the regime switch. No filler or redundancy.

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?

All five parameters are schema-documented, an output schema exists so return values need not be described, and the one non-obvious semantic (date-driven statute selection) is explained. Nothing an agent needs to invoke it correctly is missing.

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 the baseline is 3, but the description adds semantic links the schema does not: as_of_date maps to the applicable Act and regime maps to single-vs-dual computation. It does not add numeric examples or format hints for gross_income beyond the schema.

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+resource ('Compute Indian personal income tax') plus scope (dual-regime comparison for the tax year in force on as_of_date). The regime-comparison behavior and 'naming the lower one' clearly separate it from siblings like advance_tax, tds, and gst_regular.

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?

Explains that as_of_date selects the governing Act and that passing regime narrows to a single computation, which tells the agent how to steer the call. It stops short of stating when not to use it or naming an alternative sibling, so it is clear context without explicit exclusions.

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

All TrueCalci tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?