Skip to main content
Glama

Delegum

by com.delegum
OverviewDiscussionsAdmin

calcular_baja_medica

Read-only

Calcula el subsidio por incapacidad temporal (baja médica) de un trabajador por cuenta ajena: contingencia común (60% de la base los días 4-20, 75% a partir del día 21) o accidente laboral (75% desde el primer día). Devuelve el subsidio diario, mensual y total para los días de baja, y la pérdida respecto al salario habitual.

Input Schema

NameRequiredDescriptionDefault
pagasNoPagas al año: 14 si cobra dos pagas extra aparte (entran en la base prorrateadas, × 14/12); 12 si las tiene prorrateadas en la nómina mensual. Por defecto 12.
dias_bajaNoNúmero de días de baja a simular. Por defecto 30.
tipo_bajaYes"comun" = enfermedad o accidente no laboral. "accidente_laboral" = accidente de trabajo o enfermedad profesional.
salario_bruto_mensualYesSalario bruto que el trabajador cobra cada mes ordinario (€)
empresa_paga_dias_esperaNo¿La empresa cubre los 3 días de espera (según convenio)? Por defecto false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / pagas
      Added value: +{
+  "anyOf": [
+    {
+      "const": 12,
+      "type": "number"
+    },
+    {
+      "const": 14,
+      "type": "number"
+    }
+  ],
+  "description": "Pagas al año: 14 si cobra dos pagas extra aparte (entran en la base prorrateadas, × 14/12); 12 si las tiene prorrateadas en la nómina mensual. Por defecto 12."
+}
    • changedInput schema / properties / salario_bruto_mensual / description
      Previous value: -"Salario bruto mensual del trabajador (€)"New value: +"Salario bruto que el trabajador cobra cada mes ordinario (€)"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description correctly reinforcing a pure computation adds the actual calculation rules (60% days 4-20, 75% from day 21 for común; 75% from day one for accidente laboral). It also discloses the four outputs (daily, monthly, total, salary loss), which matters because there is no output schema.

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?

Just two sentences, front-loaded with the purpose and the calculation branches, with no filler. The parenthetical rule set makes the first sentence long but every clause carries information an agent needs.

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, the description takes on the return-value burden and does so by naming the four outputs. Combined with fully documented parameters and correct safety annotations, an agent has what it needs, though the lack of any usage routing to sibling tools is a small gap.

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 the schema already documents each parameter including the pagas default and the días de baja cap. The description mirrors the two contingencies that map to tipo_baja but adds no syntax or defaulting detail beyond the schema, so the baseline 3 is appropriate.

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 ('Calcula el subsidio por incapacidad temporal (baja médica) de un trabajador por cuenta ajena') and adds the two calculation branches. The qualifiers 'temporal' and 'por cuenta ajena' cleanly separate it from siblings like calcular_pension_incapacidad (permanent) and calcular_cuota_autonomo (self-employed).

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 scope makes the intended use inferable, but there is no explicit when-to-use or when-not guidance and no reference to any sibling tool. It never states, for example, that this covers only employed workers and points self-employed users elsewhere, leaving routing to inference.

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

All Delegum toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources