Skip to main content
Glama

Herramientas de Ecuador · ADVISE.ia

Calcular el décimo tercer sueldo (Ecuador)

calcular_decimo_tercero
Read-onlyIdempotent

Calcula el décimo tercer sueldo (decimotercera remuneración) de un trabajador del sector privado en Ecuador: período del 1 de diciembre al 30 de noviembre, pago acumulado hasta el 24 de diciembre, proporcional por fecha de ingreso o de salida (meses de 30 días y año de 360) o como total ganado en el período ÷ 12, y el valor mensualizado. Úsala para saber cuánto le toca a alguien de décimo tercero o cuánto va en una liquidación.

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_tercero"
  }
}

Input Schema

NameRequiredDescriptionDefault
modoNo«mensual» (con la remuneración mensual y las fechas) o «total» (total del período ÷ 12). Si falta, se deduce de los datos.
anio_pagoNoAño de pago: 2026 = período del 1-dic-2025 al 30-nov-2026 (por defecto); 2027 = del 1-dic-2026 al 30-nov-2027.
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.
remuneracion_mensualNoRemuneración mensual en USD: sueldo más horas extra, comisiones y otros pagos habituales (sin utilidades, fondo de reserva, viáticos ni décimos).
total_remuneraciones_periodoNoAlternativa: total de remuneraciones recibidas del 1 de diciembre al 30 de noviembre, en USD.

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?

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is fully covered without description help. The description adds useful domain behavior beyond that — the accrual window and the 24-December payment anchor — but says nothing about what is returned, rounding, or what happens with zero/incomplete inputs. With the annotations carrying the safety profile, a 3 is the right level.

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?

Dense but front-loaded: the tool's identity and accrual period come first, then the formula options, then the use case. It is a single long sentence plus a routing sentence, with no filler, though the parenthetical formula chain makes it heavier to scan than ideal.

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 six parameters, no required fields, two enums and no output schema, the description needs to explain the result shape and how mode inference behaves when nothing is supplied. It covers the calculation logic well but never states what the tool returns (amount only, breakdown, monthlyized value), which matters given that the output cannot be inferred from a schema.

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 the baseline is 3, and the description earns above it by clarifying cross-field behavior: modo is inferred from the supplied data, and the proportional path applies only on entry or exit within the period. The monthly remuneration definition (excludes utilidades, fondo de reserva, viáticos, décimos) is repeated from the schema rather than extending it, so it falls short of a 5.

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 names a specific verb and calculation ("Calcula el décimo tercer sueldo") and pins down the exact domain (private-sector worker in Ecuador, 1 Dec–30 Nov period, 24 Dec payment). The formula variants (proportional by entry/exit date, or total ÷ 12, plus the monthly amount) make it unmistakably distinct from siblings like calcular_decimo_cuarto or calcular_sueldo_neto_iess.

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 closing sentence gives concrete when-to-use framing: "Úsala para saber cuánto le toca a alguien de décimo tercero o cuánto va en una liquidación." That is clear context, but there are no exclusions or explicit pointers to a sibling for the liquidation case, leaving the agent to infer whether calcular_liquidacion_laboral should be preferred.

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