Skip to main content
Glama
mcp-india-stack

mcp-india-stack

calculate_leave_encashment_tax

Read-onlyIdempotent

Computes the tax-exempt portion of leave encashment under Section 10(10AA), returning the exemption amount and taxable breakdown for retirement or tax planning.

Instructions

Calculate tax-exempt portion of leave encashment under Section 10(10AA).

Use when computing leave encashment tax exemption or planning retirement benefits.

Args: leave_encashment_amount: Actual amount received average_monthly_salary: Average of last 10 months basic + DA earned_leave_balance_days: Days of earned leave years_of_service: Total years of service is_government_employee: Government employee flag

Returns: Exemption amount and taxable portion breakdown.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "leave_encashment_amount": "<leave_encashment_amount>",
      "average_monthly_salary": "<average_monthly_salary>",
      "earned_leave_balance_days": "<earned_leave_balance_days>",
      "years_of_service": "<years_of_service>"
    },
    "name": "calculate_leave_encashment_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
financial_yearNoFinancial year (e.g. '2025-26', '2026-27')2025-26
years_of_serviceYesTotal years of service
average_monthly_salaryYesAverage of last 10 months basic + DA
is_government_employeeNoGovernment employee flag
leave_encashment_amountYesActual amount received in INR
earned_leave_balance_daysYesDays of earned leave

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • addedInput schema / properties / financial_year
      Added value: +{
      +  "default": "2025-26",
      +  "description": "Financial year (e.g. '2025-26', '2026-27')",
      +  "title": "Financial Year",
      +  "type": "string"
      +}
  2. Changed8 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / average_monthly_salary / title
      Added value: +"Average Monthly Salary"
    • addedInput schema / properties / earned_leave_balance_days / title
      Added value: +"Earned Leave Balance Days"
    • addedInput schema / properties / is_government_employee / title
      Added value: +"Is Government Employee"
    • addedInput schema / properties / leave_encashment_amount / title
      Added value: +"Leave Encashment Amount"
    • addedInput schema / properties / years_of_service / title
      Added value: +"Years Of Service"
    • addedInput schema / title
      Added value: +"calculate_leave_encashment_taxArguments"
    • addedOutput schema / title
      Added value: +"calculate_leave_encashment_taxDictOutput"
  3. Addedv0.4.2

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already establish that this is a safe, idempotent, closed-world read-only computation, so the description does not need to restate that. It adds the statutory basis and says a breakdown of exemption versus taxable portion comes back, but omits the statutory caps the calculation actually hinges on (10-month average salary, 30 days per year, the overall monetary ceiling) and the effect of the government-employee flag, all of which materially change the result.

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 opening sentence is front-loaded and precise, and the Args list is easy to scan. However, the Args entries are verbatim duplicates of the schema, and the 'Returns:' block duplicates the output schema, so a meaningful share of the text does not earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the Returns section is redundant rather than necessary. More importantly, the Args list covers only 5 of the 6 parameters and silently drops financial_year, and nothing explains how the government-employee flag alters the exemption, leaving a real completeness gap for a statutory calculator.

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 baseline is 3. The Args block largely restates the schema text ('Average of last 10 months basic + DA', 'Total years of service') and adds no new meaning, and it never explains the most consequential input, is_government_employee, or what the financial_year parameter changes.

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?

Names a specific verb and resource ('Calculate tax-exempt portion of leave encashment') and anchors it to a precise statutory provision, Section 10(10AA). That makes it trivially distinguishable from the neighboring calculators such as calculate_gratuity, calculate_hra_exemption, and calculate_salary_restructuring.

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?

Explicitly states the two situations that should trigger it: computing leave encashment tax exemption and planning retirement benefits. It does not name any alternative tool or state when-not to use it (e.g. versus calculate_gratuity), so it falls short of the 5 criteria.

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