TrueCalci

India TDS (tax deducted at source)

tds

Read-onlyIdempotent

Calculate statutory Tax Deducted at Source (TDS) under the Indian Income-tax Act, 1961 (AY 2025-26 / FY 2024-25). Supports Section 194C (contractor), 194J (professional/technical fees), 194Q (goods purchase), 194H (commission/brokerage), 194I (rent), higher deduction rate under Section 206AA for missing PAN, and precedence evaluation between 194Q and 206C(1H).

Input Schema

TableJSON Schema

Name	Required	Description
`amount`	Yes	Transaction payment or credit amount in INR (₹).
`resident`	Yes	Whether the payee is resident under s.6. Non-resident payments fall under s.195 and are out of scope, so false is refused rather than answered.
`as_of_date`	Yes	Civil date YYYY-MM-DD. Selects the statutory rate pack in force on that date. Required: the engine will not assume a date.
`payee_type`	Yes	Payee class. Under s.194C this selects 1% (individual or HUF) versus 2% (domestic company), so it changes the answer and is not defaulted. The legacy values 'individual' and 'company' are still accepted as exact synonyms; any other value is refused.
`payment_type`	Yes	Statutory nature of the payment, which selects the section and therefore the rate. State it exactly; the engine does not infer it. Note that professional_services (10%) and technical_services (2%) are DISTINCT and differ fivefold - there is deliberately no combined value, and a request that does not distinguish them is answered AMBIGUOUS rather than guessed.
`pan_available`	Yes	Whether the payee has furnished a PAN. Required: without a PAN, Section 206AA applies the higher rate, so it is never assumed.
`pan_operative`	Yes	Whether the furnished PAN is operative (linked to Aadhaar). Required when pan_available is true: an inoperative PAN is treated as no PAN under Section 206AA.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`trace`	No
`reason`	No
`status`	No
`pack_id`	No
`currency`	No
`applicable`	No
`as_of_date`	No
`comparison`	No
`disclaimer`	No
`tds_amount`	No
`act_applied`	No
`escalations`	No
`liable_base`	No
`minor_units`	No
`net_payable`	No
`on_crossing`	No
`return_form`	No
`act_2025_ref`	No
`payment_code`	No
`rule_ids_used`	No
`crossing_basis`	No
`effective_rate`	No
`engine_version`	No
`legacy_section`	No
`threshold_value`	No
`certificate_form`	No
`deposit_due_date`	No
`preimage_version`	No
`consumed_input_fields`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "act_2025_ref": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "act_applied": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "applicable": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "as_of_date": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "certificate_form": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "comparison": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "consumed_input_fields": {
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "crossing_basis": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "currency": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "deposit_due_date": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "disclaimer": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "effective_rate": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "engine_version": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "escalations": {
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "legacy_section": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "liable_base": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "minor_units": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "net_payable": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "on_crossing": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "pack_id": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "payment_code": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "preimage_version": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "reason": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "return_form": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "rule_ids_used": {
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "status": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "tds_amount": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "threshold_value": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "trace": {
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed6 schema fields changedSep 26, 2026

addedInput schema / properties / amount / example
```
Added value: +"50000.00"
```
addedInput schema / properties / amount / pattern
```
Added value: +"^\\d+\\.\\d{2}$"
```

changedInput schema / properties / amount / type

Previous value: -"number"New value: +"string"

changedInput schema / properties / pan_available / description

Previous value: -"Whether the payee has furnished a valid PAN. false triggers the s.206AA higher rate of 20%."New value: +"Whether the payee has furnished a PAN. Required: without a PAN, Section 206AA applies the higher rate, so it is never assumed."

addedInput schema / properties / pan_operative

Added value: +{
+  "description": "Whether the furnished PAN is operative (linked to Aadhaar). Required when pan_available is true: an inoperative PAN is treated as no PAN under Section 206AA.",
+  "type": "boolean"
+}

changedInput schema / required

Previous value: -[
-  "amount",
-  "as_of_date",
-  "payment_type",
-  "payee_type",
-  "resident"
-]New value: +[
+  "amount",
+  "as_of_date",
+  "payment_type",
+  "payee_type",
+  "resident",
+  "pan_available",
+  "pan_operative"
+]

Changed12 schema fields changedSep 24, 2026

addedInput schema / properties / as_of_date

Added value: +{
+  "description": "Civil date YYYY-MM-DD. Selects the statutory rate pack in force on that date. Required: the engine will not assume a date.",
+  "type": "string"
+}

addedInput schema / properties / pan_available

Added value: +{
+  "description": "Whether the payee has furnished a valid PAN. false triggers the s.206AA higher rate of 20%.",
+  "type": "boolean"
+}

removedInput schema / properties / pan_status

Removed value: -{
-  "default": "valid",
-  "description": "Status of payee PAN. 'missing_or_invalid' triggers Section 206AA higher withholding rate (20%).",
-  "enum": [
-    "valid",
-    "missing_or_invalid"
-  ],
-  "type": "string"
-}

removedInput schema / properties / payee_type / default
```
Removed value: -"individual"
```

changedInput schema / properties / payee_type / description

Previous value: -"Legal entity classification of the payee."New value: +"Payee class. Under s.194C this selects 1% (individual or HUF) versus 2% (domestic company), so it changes the answer and is not defaulted. The legacy values 'individual' and 'company' are still accepted as exact synonyms; any other value is refused."

changedInput schema / properties / payee_type / enum

Previous value: -[
-  "individual",
-  "company"
-]New value: +[
+  "individual_or_huf",
+  "domestic_company"
+]

removedInput schema / properties / payment_type / default
```
Removed value: -"contract"
```

changedInput schema / properties / payment_type / description

Previous value: -"Statutory nature of payment under the Income-tax Act."New value: +"Statutory nature of the payment, which selects the section and therefore the rate. State it exactly; the engine does not infer it. Note that professional_services (10%) and technical_services (2%) are DISTINCT and differ fivefold - there is deliberately no combined value, and a request that does not distinguish them is answered AMBIGUOUS rather than guessed."

changedInput schema / properties / payment_type / enum

Previous value: -[
-  "contract",
-  "technical_professional",
-  "goods_purchase",
-  "commission_brokerage",
-  "rent_land_building",
-  "rent_plant_machinery"
-]New value: +[
+  "contract",
+  "professional_services",
+  "technical_services",
+  "purchase_of_goods",
+  "royalty",
+  "director_fees",
+  "non_compete_fees",
+  "call_centre"
+]

addedInput schema / properties / resident

Added value: +{
+  "description": "Whether the payee is resident under s.6. Non-resident payments fall under s.195 and are out of scope, so false is refused rather than answered.",
+  "type": "boolean"
+}

removedInput schema / properties / resident_status

Removed value: -{
-  "default": "resident",
-  "description": "Residential status of the payee under Section 6.",
-  "enum": [
-    "resident",
-    "non_resident"
-  ],
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "amount"
-]New value: +[
+  "amount",
+  "as_of_date",
+  "payment_type",
+  "payee_type",
+  "resident"
+]

AddedSep 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds meaningful domain behavior beyond annotations: higher deduction rate under Section 206AA for missing PAN and precedence evaluation between 194Q and 206C(1H). It stops short of disclosing the refusal for non-resident payments (that appears only in the schema), but still contributes useful behavioral context.

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?

The description is two sentences, front-loaded with the core purpose, followed by supported sections and special rules. Every clause earns its place, and there is no redundant or filler content. It is appropriately sized for a complex statutory calculation tool.

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?

Given the complexity, rich schema, annotations, and existing output schema, the description covers the essential scope (Act, assessment year, supported sections, key rules). It does not mention the out-of-scope handling for non-resident payments or the mandatory date selection, but those details are fully documented in the schema. The description is largely complete, with only minor contextual gaps that the structured fields already fill.

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 description coverage is 100%, so the structured schema already documents all seven parameters in detail. The description adds no parameter-level syntax, format, or constraint information beyond what the schema provides. A baseline score of 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb ('Calculate') and resource ('Tax Deducted at Source') within a precise legal context (Indian Income-tax Act, 1961, AY 2025-26). It lists the supported sections, which clearly distinguishes it from siblings like tcs or gst_regular. An agent can immediately tell this is a statutory TDS calculator for India.

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

Usage Guidelines3/5

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

The description implies usage by enumerating supported sections and special rules (missing PAN, 194Q vs 206C(1H) precedence), but it never explicitly states when to choose this tool over alternatives such as tcs or advance_tax. There is no 'when-not-to-use' or sibling routing guidance. The schema descriptions carry the burden of prerequisites and refusals, so the description's guidance is minimal but not absent.

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?