Skip to main content
Glama

Herramientas de Ecuador · ADVISE.ia

Calcular el sueldo neto y los aportes al IESS (Ecuador)

calcular_sueldo_neto_iess
Read-onlyIdempotent

Calcula el sueldo neto mensual y anual de un trabajador en relación de dependencia del sector privado en Ecuador y lo que cuesta a la empresa: aporte personal al IESS 9,45 %, aporte patronal 11,15 %, fondo de reserva 8,33 % (desde el segundo año, en el rol o acumulado en el IESS) y décimo tercero y décimo cuarto mensualizados o acumulados. Úsala cuando pregunten cuánto recibe alguien con cierto sueldo, cuánto le descuenta el IESS o cuánto le cuesta un empleado a la empresa. No descuenta impuesto a la renta, préstamos ni anticipos.

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

Input Schema

NameRequiredDescriptionDefault
fondo_reservaNo«mensual» = el fondo de reserva se paga en el rol (por defecto); «acumulado» = se deposita en el IESS.
mas_de_un_anioNotrue si lleva más de un año con el mismo empleador, lo que activa el fondo de reserva (por defecto true).
otros_ingresosNoHoras extra, comisiones y otros ingresos habituales del mes que aportan al IESS, en USD (por defecto 0).
salario_basicoNoSalario básico unificado en USD (por defecto 482, el de 2026).
sueldo_mensualYesSueldo mensual bruto en USD.
horas_semanalesNoHoras semanales de la jornada (40 = completa, por defecto).
decimo_cuarto_mensualNotrue si cobra el décimo cuarto cada mes (por defecto true).
decimo_tercero_mensualNotrue si cobra el décimo tercero cada mes (por defecto true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, and the description adds substantial context: exact contribution rates (9.45%, 11.15%, 8.33%), the second-year condition for fondo de reserva, and which deductions are deliberately excluded. It stops short of describing return structure or rounding rules, so a 4 rather than 5.

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 core computation and its components come first, followed by usage triggers and exclusions. The single long sentence packs many rates but every clause earns its place; minor density cost keeps it from a 5.

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 no output schema and eight parameters, the description adequately explains the domain model and what the result conceptually contains (net monthly and annual salary, employer cost). It does not spell out the exact output fields, but coverage is sufficient to call the tool correctly.

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 all eight parameters including enums and defaults are already documented in the schema. The description reinforces domain meaning (rates, mensualizado vs acumulado) but adds little parameter-level detail beyond the schema, matching the baseline 3.

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?

States a specific verb and resource (compute net monthly/annual salary and IESS contributions for a private-sector employee in Ecuador) and explicitly scopes what it covers and what it does not. The mention that income tax, loans and advances are not deducted makes it clearly distinguishable from siblings like calcular_impuesto_renta_2026 or calcular_liquidacion_laboral.

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?

Provides explicit usage triggers ('cuándo pregunten cuánto recibe... cuánto le descuenta el IESS... cuánto le cuesta a la empresa') and a clear exclusion list. It does not name specific alternative tools for the excluded computations, which keeps it from a 5.

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