Mexican Payroll & Tax Calculator

calc_finiquito

Compute a Mexican finiquito/liquidación (severance) for a resignation or an unjustified dismissal: prorated christmas bonus, vacations, vacation premium, pending salary, and (for dismissal) 90-day + 20-day/year severance and the seniority premium, with Art. 93 exemptions and separation ISR. Do NOT compute this from memory — LFT bands, UMA exemptions, and the SDI integration factor are table-driven. Returns per-concept gross/exempt/taxable, totals, ISR, deductions, and net_total.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`year`	No	Tax-table year.
`zone`	No	Minimum-wage zone.	general
`hire_date`	Yes	Hire date, YYYY-MM-DD.
`deductions`	No	Optional pass-through deductions.
`daily_salary`	Yes	Daily salary (MXN).
`pending_days`	No	Unpaid worked days pending.
`paid_in_january`	No	January UMA boundary.
`termination_date`	Yes	Termination date, YYYY-MM-DD.
`termination_type`	Yes	Type of separation.
`vacation_proration`	No	Vacation proration basis.	anniversary
`prima_vacacional_pct`	No	Vacation premium percentage (defaults to the legal 25%).
`monthly_ordinary_salary`	No	Monthly ordinary salary for ISR (defaults to daily x 30.4).
`include_20_days_per_year`	No	Include the 20-day/year dismissal indemnity.

TDQS

A4.2/5.0

Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses the return structure (per-concept gross/exempt/taxable, totals, ISR, deductions, net_total) and mentions legal references (LFT, UMA, SDI). For a computation tool, this is sufficient and allows agents to understand behavior.

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 two sentences long, front-loading the tool's purpose and listing key outputs. No redundant information. Every sentence adds value, making it highly efficient.

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?

Despite no output schema, the description specifies the return structure. With 13 parameters (4 required) and complex legal logic, the description is fairly complete. It covers what the tool computes without explaining every edge case or error handling, which is acceptable for this complexity.

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% for all 13 parameters. The description does not add parameter-level detail beyond listing the computed concepts (e.g., prorated Christmas bonus, vacations). Since the schema already describes each parameter, the description provides no additional semantic value for individual parameters.

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 clearly states the tool computes a Mexican finiquito/liquidación for resignation or dismissal, listing the specific components (prorated Christmas bonus, vacations, etc.). It differentiates itself from sibling tools (calc_aguinaldo, calc_imss, calc_isr) by focusing on severance calculation.

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 advises against manual computation ('Do NOT compute this from memory') and references legal tables, implying the tool should be used for accurate calculations. It does not explicitly state when to use alternatives, but sibling tools cover different aspects (e.g., aguinaldo, IMSS, ISR).

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

All Mexican Payroll & Tax Calculator 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.1/5.0

Disambiguation5/5

Each tool targets a distinct and well-defined payroll/tax concept (aguinaldo, finiquito, IMSS, ISR) with no functional overlap, making it easy for an agent to select the correct one.

Naming Consistency5/5

All tool names follow a consistent 'calc_' prefix plus a specific concept (calc_aguinaldo, calc_finiquito, calc_imss, calc_isr), using snake_case throughout.

Tool Count5/5

Four tools is an appropriate scope for a payroll/tax calculator, covering the essential mandatory calculations without being overly granular or sparse.

Completeness4/5

The tools cover the main Mexican payroll obligations (year-end bonus, severance, social security, income tax). Minor gaps like profit sharing (PTU) or annual tax return are absent, but the core is well-covered.

Resources

Need Help?