Skip to main content
Glama

FinanceGenius.AI

Calculate Indian income tax

calculate_indian_income_tax
Read-only

Compute Indian income tax for FY 2025-26 under old or new regime.

    Args:
        annual_income: Gross annual income in rupees.
        regime: 'new' (default) or 'old'.
        deductions_80c: Section 80C deductions in rupees (max ₹1,50,000, old regime only).
        deductions_80d: Section 80D health-insurance premium (old regime only).
        hra_exemption: HRA exemption amount (old regime only).

    Returns:
        Slab breakdown, total tax, effective rate, regime comparison.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regimeNonew
annual_incomeYes
hra_exemptionNo
deductions_80cNo
deductions_80dNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations confirm this is a safe read-only, non-destructive, closed-world calculation. The description adds that it returns a slab breakdown, total tax, effective rate, and regime comparison, which is useful return info not covered by annotations. However, it doesn't clarify edge cases, rounding, or whether assumptions are documented.

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?

Uses a structured Args/Returns format that is front-loaded and information-dense without wasted sentences. Slightly verbose for an agent but well organized and every section earns its place.

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?

No output schema exists, so the description usefully summarizes returns. Parameter semantics are strong. Missing explicit usage guidance and edge-case behavior, but overall sufficient for a read-only calculation tool.

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 description coverage is 0%, so the description must carry parameter meaning. It documents units (rupees), defaults ('new'), maximum cap for 80C (₹1,50,000), and regime applicability for 80D and HRA. This substantially compensates for the schema's lack of descriptions.

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 (Compute) and resource (Indian income tax) with version/regime scope (FY 2025-26, old/new). Clearly distinguishable from the financial calculator siblings like calculate_emi or calculate_cagr.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool vs siblings or when not to use it. Domain is evident from the name, but alternatives like explain_financial_concept are not addressed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources