Skip to main content
Glama

Herramientas de Ecuador · ADVISE.ia

Calcular el décimo cuarto sueldo (Ecuador)

calcular_decimo_cuarto
Read-onlyIdempotent

Calcula el décimo cuarto sueldo (decimocuarta remuneración) de un trabajador del sector privado en Ecuador: un salario básico unificado por año (SBU 2026 USD 482), proporcional a los días trabajados (año de 360) y a la jornada parcial. Costa y Galápagos: período del 1 de marzo al último día de febrero, pago hasta el 15 de marzo. Sierra y Amazonía: del 1 de agosto al 31 de julio, pago hasta el 15 de agosto. Incluye el valor mensualizado. Úsala para saber cuánto le toca a alguien de décimo cuarto.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calcular_decimo_cuarto"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNo«costa» = Costa y Galápagos (por defecto); «sierra» = Sierra y Amazonía.
anio_pagoNoAño de pago (por defecto 2027). Costa 2027: 1-mar-2026 a 28-feb-2027; Sierra 2027: 1-ago-2026 a 31-jul-2027. Con 2026, los períodos del año anterior.
fecha_salidaNoFecha de salida (AAAA-MM-DD), solo si salió antes del cierre del período.
fecha_ingresoNoFecha de ingreso (AAAA-MM-DD), solo si entró después de que empezó el período.
salario_basicoNoSalario básico unificado en USD (por defecto 482, el de 2026; cámbialo si el Ministerio del Trabajo fija otro).
horas_semanalesNoHoras semanales de la jornada (40 = completa, por defecto; con jornada parcial se paga en proporción).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description goes further by disclosing the computation model: one SBU per year, proportional to days worked on a 360-day year, pro-rated for partial jornada, plus a monthly-installment value. That is genuine behavioral context an agent cannot read off the annotations. It stops short of saying what the response contains structurally.

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 core definition, then regional periods, then the monthly-value note; nearly every clause carries domain information. The single long sentence packs a lot, though the trailing 'Úsala para…' sentence is largely redundant with the opening.

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?

With no output schema, the description must convey the return shape, and it only hints that a monthlyized value is included without naming the fields (base amount, proportional days, period dates, monthly installment). For a six-parameter, zero-required calculator the input side is well covered via the schema, but the result side is left to inference.

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 region, anio_pago, dates, salario_basico and horas_semanales are already documented in detail, giving a baseline of 3. The description adds little parameter-level meaning beyond the schema apart from the 360-day year convention reinforcing how fecha_ingreso/fecha_salida are pro-rated.

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?

States a specific verb and resource (calcula el décimo cuarto sueldo) and pins the domain tightly to private-sector workers in Ecuador, so an agent knows exactly what benefit is computed. It does not explicitly contrast with siblings such as calcular_decimo_tercero or calcular_liquidacion_laboral, which also touch labor benefits, so differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The closing line 'Úsala para saber cuánto le toca a alguien de décimo cuarto' only restates the purpose rather than defining when to use this versus another calculator. The regional period/payment-date rules implicitly tell the agent when each region configuration applies, but there are no exclusions (e.g., public sector, termination settlements handled elsewhere).

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