Skip to main content
Glama

Herramientas de Ecuador · ADVISE.ia

Calcular horas extra (Ecuador)

calcular_horas_extra
Read-onlyIdempotent

Calcula el pago de horas extra de un trabajador con jornada completa de 40 horas en Ecuador: valor de la hora = sueldo ÷ 240; horas suplementarias con recargo de 50 % hasta las 24:00 y de 100 % entre las 24:00 y las 06:00; extraordinarias (sábado, domingo o feriado) con 100 %; recargo nocturno de 25 % para horas de la jornada entre las 19:00 y las 06:00. Incluye el aporte personal al IESS sobre las horas extra y revisa el límite de 12 horas suplementarias a la semana. Úsala cuando pregunten cuánto se paga por horas extra o cuánto vale la hora de trabajo.

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": {
      "sueldo_mensual": "<sueldo_mensual>"
    },
    "name": "calcular_horas_extra"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodoNoSi las horas son de un «mes» (por defecto) o de una «semana» (con semana se revisa el límite de 12 horas suplementarias).
madrugadaNoHoras suplementarias entre las 24:00 y las 06:00 (+100 %).
nocturnasNoHoras de la jornada ordinaria entre las 19:00 y las 06:00: se paga solo el recargo de 25 %.
sueldo_mensualYesSueldo mensual en USD (la remuneración de la jornada ordinaria, sin horas extra).
suplementariasNoHoras suplementarias hasta las 24:00, de lunes a viernes (+50 %).
extraordinariasNoHoras en sábado, domingo o feriado (+100 %).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description still adds real behavior: it discloses the IESS personal contribution, the 12-hour weekly limit check, and the implicit assumption of a 40-hour full-time worker — useful context. However it never says what the result looks like (a single amount vs. an itemized breakdown per hour type), which is the main behavioral unknown left for a pure computation tool.

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?

Front-loaded with the verb and the formula, then the rate rules, then the usage sentence — a logical progression with no filler. It is dense (one very long sentence carrying five surcharge rules), which is efficient but makes the rate table harder to scan than a short enumerated list would be.

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?

For a 6-parameter computation tool with no output schema, the description should at least sketch the shape of the returned result (total amount, per-category breakdown, limit warning). It covers inputs well and mentions the IESS deduction and weekly-limit review, but not whether the 12-hour limit is an error or a warning, nor what the response contains.

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?

Schema coverage is 100%, so baseline is 3, and the description goes beyond it by giving the model behind sueldo_mensual (÷240 hourly value) and mapping each hour category to its surcharge (suplementarias +50% until 24:00, madrugada +100%, extraordinarias +100%, nocturnas +25%), which reinforces the enum and the hour-type parameters. It does not explain how periodo interact with the weekly limit beyond what the schema already says, so it is not fully additive.

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?

Opens with a specific verb and resource ("Calcula el pago de horas extra de un trabajador") and immediately pins the scope (jornada completa de 40 horas, Ecuador), then gives the exact formula (sueldo ÷ 240). An agent can tell this apart from sueldo_neto_iess or liquidacion_laboral without opening any schema.

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 when to use it: "Úsala cuando pregunten cuánto se paga por horas extra o cuánto vale la hora de trabajo." That covers the main trigger with a concrete condition, but it names no alternative sibling for overlapping payroll questions (e.g., net salary with IESS), leaving routing in edge cases to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources