Skip to main content
Glama
rehan1020

mcp-india-stack

by rehan1020
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

calculate_advance_tax

Read-onlyIdempotent

Calculate quarterly advance tax instalments with due dates under Sections 234B and 234C, helping you plan payments and avoid interest penalties.

Instructions

Calculate quarterly advance tax installment schedule per Sections 234B and 234C.

Use when planning quarterly tax payments to avoid interest penalties. Provides due dates and amounts for each installment.

Args: estimated_income: Estimated annual income for FY2025-26. regime: Tax regime for calculation. taxpayer_type: Category for slab selection. existing_tds: TDS already likely to be deducted.

Returns: Standard envelope with quarterly breakdown and interest rules.

Notes: Due dates: June 15 (15%), Sept 15 (45%), Dec 15 (75%), Mar 15 (100%). Interest 1% per month for delay under Section 234C.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regimeNo'new' or 'old' tax regimenew
existing_tdsNoTDS already deducted or to be deducted in rupees
taxpayer_typeNo'individual', 'senior_citizen', or 'super_senior_citizen'individual
estimated_incomeYesEstimated total income for FY in rupees

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / estimated_income / title
      Added value: +"Estimated Income"
    • addedInput schema / properties / existing_tds / title
      Added value: +"Existing Tds"
    • addedInput schema / properties / regime / title
      Added value: +"Regime"
    • addedInput schema / properties / taxpayer_type / title
      Added value: +"Taxpayer Type"
    • addedInput schema / title
      Added value: +"calculate_advance_taxArguments"
    • addedOutput schema / title
      Added value: +"calculate_advance_taxDictOutput"
  2. First observedv0.3.0

TDQS

A4.5/5.0
Behavior4/5

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

With annotations already establishing readOnly and idempotent behavior, the description augments them by explaining the concrete calculation rules: specific quarterly due dates with cumulative percentages and a 1% per month interest rule. It also states the return envelope contains the schedule and interest rules, going beyond the bare annotation information.

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 well organized with a one-sentence summary, a usage sentence, and a clear Args/Returns/Notes layout. Every line adds information about inputs, output shape, or the underlying calculation rules, and there is no redundant or fragmented content.

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?

Given that the output schema already carries return details, the description covers the remaining context needed for a computation of tool: the practical scenario, the fiscal year, the expected due dates, and the interest rule. An agent is equipped to use it without ambiguous assumptions.

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?

Input schema coverage is 100%, but the description enriches a few parameters: it ties estimated_income to FY2025-26, explains taxpayer_type as 'category for slab selection,' and frames existing_tds as 'likely' deductible TDS. These small nuances clarify intent beyond the schema descriptions alone.

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 quarterly advance tax installment schedule per Sections 234B and 234C.' This clearly identifies the tool's output and differentiates it from siblings like calculate_income_tax or calculate_tds, since it focuses on installment scheduling and specific legal sections.

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 text provides a clear use case: 'Use when planning quarterly tax payments to avoid interest penalties.' This tells the agent when to invoke the tool, though it does not explicitly name alternative tools or situations to avoid, which keeps it a step below full exclusion guidance.

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