Skip to main content
Glama
rehan1020

mcp-india-stack

by rehan1020
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

calculate_hra_exemption

Read-onlyIdempotent

Calculate House Rent Allowance exemption under Section 10(13A) by taking the minimum of HRA received, rent paid minus 10% of salary, and 50%/40% of salary based on city type, for accurate tax filing.

Instructions

Calculate House Rent Allowance (HRA) exemption under Section 10(13A).

Use when computing tax-exempt HRA component for salary structuring or income tax filing. Compares three conditions and takes minimum.

Args: basic_salary: Monthly basic salary. hra_received: Annual HRA received from employer. rent_paid: Annual rent paid. city_type: 'metro' (50% of salary) or 'non_metro' (40% of salary). is_government_employee: Use simplified formula for government employees.

Returns: Standard envelope with exemption amount, taxable HRA, and breakdown.

Notes: The actual exemption is the minimum of: 1. HRA received 2. Rent paid minus 10% of salary 3. 50% of salary (metro) or 40% (non_metro)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
city_typeNo'metro' (Delhi/Mumbai/Chennai/Kolkata) or 'non_metro'non_metro
rent_paidYesAnnual rent paid in rupees
basic_salaryYesMonthly basic salary in rupees
hra_receivedYesAnnual HRA received from employer in rupees
is_government_employeeNoTrue for government employees using simplified formula

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 / basic_salary / title
      Added value: +"Basic Salary"
    • addedInput schema / properties / city_type / title
      Added value: +"City Type"
    • addedInput schema / properties / hra_received / title
      Added value: +"Hra Received"
    • addedInput schema / properties / is_government_employee / title
      Added value: +"Is Government Employee"
    • addedInput schema / properties / rent_paid / title
      Added value: +"Rent Paid"
    • addedInput schema / title
      Added value: +"calculate_hra_exemptionArguments"
    • addedOutput schema / title
      Added value: +"calculate_hra_exemptionDictOutput"
  2. First observedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already provide readOnlyHint and idempotentHint, so the no-side-effect behavior is covered. The description adds useful behavioral detail: the exemption is the minimum of three conditions, government employees use a simplified formula, and the return includes exemption, taxable HRA, and breakdown. This goes beyond the structured fields.

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 well front-loaded with the core purpose, followed by a structured Args, Returns, and Notes section. It is somewhat repetitive with the schema but the formula notes earn their place. The overall length is justified.

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 description given the tool's moderate complexity covers the calculation rule, the parameter semantics, and the returned envelope. There is also an output schema, so the return shape does not need desktop enumeration. This is sufficient for an agent to select and invoke the tool correctly.

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?

Although schema description coverage is 100%, the description adds extra semantic value by explaining metro vs non_metro as 50%/40% of salary and clarifying government employees use a simplified formula. It also restates input units (monthly/rupees), making each parameter's role easier to interpret.

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 states a specific verb and resource — 'calculate House Rent Allowance (HRA) exemption under Section 10(13A)' — so the agent knows exactly what function is being performed. It also narrows scope to tax-exempt HRA for salary structuring and income tax filing, which clearly separates it from the many sibling tax/income calculator tools.

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 gives clear conditions: 'Use when computing tax-exempt HRA component for salary structuring or income tax filing.' This is actionable and context-specific, though it does not name sibling tools to exclude or state when not to use this calculator.

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