mcp-india-stack

by rehan1020

Overview Schema Source Related Servers Discussions Admin

Python

Local

calculate_income_tax_interest

Read-onlyIdempotent

Compute penalty interest under Sections 234A, 234B, and 234C for late tax filing or short advance tax payments.

Instructions

Calculate interest under Sections 234A, 234B, 234C.

Use when computing penalty interest for late tax filing or short advance tax payments.

Args: total_tax_liability: Total tax liability tds_deducted: TDS already deducted advance_tax_paid: Dict with q1,q2,q3,q4 quarterly payments filing_date: YYYY-MM-DD when return filed (None if not filed) due_date: Due date for filing

Returns: Interest breakdown for Sections 234A, 234B, 234C.

Input Schema

Name	Required	Description	Default
`due_date`	No	Due date YYYY-MM-DD	2025-07-31
`filing_date`	No	Filing date YYYY-MM-DD or None if not filed
`tds_deducted`	No	TDS already deducted in INR
`financial_year`	No	Financial year (e.g. '2025-26', '2026-27')	2025-26
`advance_tax_paid`	No	Dict with q1,q2,q3,q4 quarterly payments
`total_tax_liability`	Yes	Total tax liability in INR

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.8.0Nov 5, 2026

addedInput schema / properties / financial_year

Added value: +{
+  "default": "2025-26",
+  "description": "Financial year (e.g. '2025-26', '2026-27')",
+  "title": "Financial Year",
+  "type": "string"
+}

Changed8 schema fields changedv0.5.0Aug 25, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / advance_tax_paid / title
```
Added value: +"Advance Tax Paid"
```
- addedInput schema / properties / due_date / title
```
Added value: +"Due Date"
```
- addedInput schema / properties / filing_date / title
```
Added value: +"Filing Date"
```
- addedInput schema / properties / tds_deducted / title
```
Added value: +"Tds Deducted"
```
- addedInput schema / properties / total_tax_liability / title
```
Added value: +"Total Tax Liability"
```
- addedInput schema / title
```
Added value: +"calculate_income_tax_interestArguments"
```
- addedOutput schema / title
```
Added value: +"calculate_income_tax_interestDictOutput"
```
Addedv0.4.2Jun 8, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds the relevant sections and the triggering scenarios, but it does not disclose the calculation rules, rate assumptions, or other behavioral details for a financial computation.

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 front-loaded with the core purpose and usage, then organized into Args and Returns sections. It is efficient overall, though portions of the Args section duplicate the schema.

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 six parameters and an output schema, the description is mostly complete: it explains the purpose, usage condition, key inputs, and return categories. The main gap is that financial_year is not mentioned in the Args section, but the schema supplies it with a default.

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 schema already documents the parameters. The description repeats most parameter meanings, including the advance-tax quarterly dict, but omits the financial_year parameter entirely; this is acceptable because the schema covers it, but it adds little beyond the schema.

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 states a specific verb+resource: calculating interest under Sections 234A, 234B, and 234C. It clearly scopes the tool to penalty interest, which differentiates it from generic tax calculators in the sibling list, though it does not explicitly name an alternative.

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?

It gives clear usage context: 'Use when computing penalty interest for late tax filing or short advance tax payments.' This tells the agent when to use it, but it does not state when not to use it or name specific alternative tools.

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

Deploy Server