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

Name	Required	Default
`regime`	No	new
`annual_income`	Yes
`hra_exemption`	No
`deductions_80c`	No
`deductions_80d`	No

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already mark the tool as read-only and non-destructive. The description adds useful behavioral context by specifying the return payload — slab breakdown, total tax, effective rate, and regime comparison — and by documenting regime-specific deduction rules. No contradiction with annotations exists.

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 compact and well-structured: a one-line purpose statement followed by an Args/Returns block. There is no filler, and the key scoping information (FY, regimes, deduction limits) is front-loaded.

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?

For a five-parameter tool with no output schema and a nuanced tax domain, the description is complete enough for correct invocation. It documents all parameter semantics, regime restrictions, and the expected return contents. Additional internal details like surcharge or slab rates are not required to call the tool successfully.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden for parameter meaning. It explains each parameter, including that annual_income is gross income in rupees, regime defaults to 'new', 80C has a ₹1,50,000 cap, and 80C/80D/HRA apply only to the old regime. This is exactly what an agent needs beyond the bare schema titles.

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 pairs a specific verb ('Compute') with a precise resource ('Indian income tax for FY 2025-26') and names both tax regimes. This makes the tool's purpose unmistakable and clearly distinct from sibling calculators 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 Guidelines4/5

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

The first line establishes the target use case, and the Args section gives practical selection guidance: deductions and HRA are applicable only under the old regime, while the new regime is the default. It does not explicitly name alternatives, but the tax-specific context and sibling names make the intended usage clear.

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

All FinanceGenius.AI tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: the calculate_* tools cover different financial formulas, find_best_* tools recommend different product types, and search/get/compare form a coherent product workflow. There is no realistic ambiguity between tools despite the overlap in financial domain.

Naming Consistency5/5

Tool names consistently follow a verb-first snake_case pattern, with clear groupings like calculate_*, find_best_*, and get_*. Minor use of abbreviations like CAGR and EMI is natural and does not break the naming convention.

Tool Count5/5

12 tools is well-scoped for a personal finance assistant covering calculators, product search, product details, comparisons, recommendations, and concept explanations. Each tool earns its place without redundancy or bloat.

Completeness4/5

The tool set covers core financial calculations, product discovery, comparison, recommendations, and educational explanations, which is strong for the stated purpose. Minor gaps exist around loan/insurance product comparisons and more advanced investment planning, but agents can accomplish most typical finance workflows.

Resources

Need Help?