Skip to main content
Glama
mcp-india-stack

mcp-india-stack

calculate_epf_esic

Read-onlyIdempotent

Calculate EPF and ESIC contributions from basic and gross wages to estimate employee deductions, employer costs, and payroll CTC.

Instructions

Calculate EPF and ESIC contributions for employer and employee.

Use when computing payroll costs, employee deductions, or comparing CTC structures across different salary levels.

Args: basic_wages: Basic salary + DA per month in INR. gross_wages: Total gross monthly salary in INR. include_employer_share: If True, return employer costs.

Returns: Standard envelope with EPF breakdown, ESIC applicability, and totals.

Notes: EPF ceiling is ₹15,000/month for statutory computation. ESIC applicable when gross wages ≤ ₹21,000/month.

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": {
      "basic_wages": "<basic_wages>",
      "gross_wages": "<gross_wages>"
    },
    "name": "calculate_epf_esic"
  }
}

Input Schema

NameRequiredDescriptionDefault
basic_wagesYesBasic salary + DA per month in INR
gross_wagesYesTotal gross monthly salary in INR
financial_yearNoFinancial year (e.g. '2025-26', '2026-27')2025-26
include_employer_shareNoIf True, return employer costs

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. Changed6 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / basic_wages / title
      Added value: +"Basic Wages"
    • addedInput schema / properties / gross_wages / title
      Added value: +"Gross Wages"
    • addedInput schema / properties / include_employer_share / title
      Added value: +"Include Employer Share"
    • addedInput schema / title
      Added value: +"calculate_epf_esicArguments"
    • addedOutput schema / title
      Added value: +"calculate_epf_esicDictOutput"
  3. Addedv0.4.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world behavior, so safety is covered. The description adds genuinely useful domain rules (EPF ceiling ₹15,000/month, ESIC applicability at gross ≤ ₹21,000/month), but the 'Returns' sentence merely restates the output envelope that the output schema already defines.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and usage are front-loaded and easy to scan, and the Notes section carries unique value. However, the Args block and the Returns line largely repeat the input and output schemas, 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.

Completeness4/5

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

With an output schema present and annotations covering the safety profile, the description does not need to explain return format. It supplies the two statutory thresholds an agent needs to interpret results correctly; the only gap is that the financial_year parameter's effect on rates is left to the schema.

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 coverage is 100%, so all four parameters are already documented in the schema. The Args block duplicates those descriptions almost verbatim rather than adding interpretation, such as whether basic_wages should be capped before applying the EPF ceiling.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource: computing EPF and ESIC contributions split by employer and employee share. It is clearly distinguishable from neighbors like validate_epf_code or calculate_professional_tax, though it does not call out any sibling by name.

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 'Use when' sentence gives concrete triggers: payroll cost computation, employee deductions, and CTC comparison across salary levels. There are no explicit exclusions or pointers to alternatives such as calculate_salary_restructuring, which keeps it below a 5.

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