Skip to main content
Glama
rehan1020

mcp-india-stack

by rehan1020
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

calculate_income_tax_interest

Read-onlyIdempotent

Compute penalty interest under Income Tax Sections 234A, 234B, and 234C for late filing or short advance tax payments. Enter tax liability, TDS, quarterly advance tax, and filing date to get an instant interest breakdown.

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

TableJSON Schema
NameRequiredDescriptionDefault
due_dateNoDue date YYYY-MM-DD2025-07-31
filing_dateNoFiling date YYYY-MM-DD or None if not filed
tds_deductedNoTDS already deducted in INR
advance_tax_paidNoDict with q1,q2,q3,q4 quarterly payments
total_tax_liabilityYesTotal tax liability in INR

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.5.0
    • 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"
  2. Addedv0.4.2

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, which cover the safety profile for this pure calculation tool. The description adds that it calculates penalty interest and returns a breakdown, but it does not go deeper into assumptions, formatting, or edge cases. It remains consistent with annotations.

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 concise and front-loaded, with the core purpose stated in the first line and a direct usage guideline next. The Args and Returns sections are somewhat redundant with the structured schema, but they remain brief and do not bloat the description.

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?

The tool is a calculation utility with full schema coverage and an output schema. The description provides enough context about when to use it, which sections it covers, and what inputs are relevant. Nothing essential for an agent to select and invoke this tool correctly is missing.

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 every parameter. The description repeats the parameter names and brief meanings without adding new semantics beyond what the schema provides, such as units or calculation rules. This matches the baseline of 3.

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 opens with a specific verb and resource: 'Calculate interest under Sections 234A, 234B, 234C.' It names the exact tax provisions and clarifies the purpose as computing penalty interest, distinguishing it from sibling calculation tools like calculate_income_tax and calculate_advance_tax.

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?

The description explicitly states when to use this tool: 'Use when computing penalty interest for late tax filing or short advance tax payments.' It gives clear usage context, though it does not explicitly name alternative tools or exclude scenarios where this tool should not be used.

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