Skip to main content
Glama

Delegum

by com.delegum

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

TableJSON Schema
NameRequiredDescriptionDefault
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 mensual del trabajador (€)
empresa_paga_dias_esperaNo¿La empresa cubre los 3 días de espera (según convenio)? Por defecto false.

TDQS

A4/5.0
Behavior4/5

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

Annotations already provide readOnlyHint=true, which the description complements. The description discloses the calculation formulas (60%/75% for common, 75% for accidents) and return details (daily, monthly, total, loss). No contradictions with annotations.

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?

The description is concise (one sentence) but packs necessary information: calculation rules, return types, and contingencies. It is well-structured and clearly worded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool is a calculator with complete schema descriptions and annotations, the description covers the calculation logic and output values adequately. No output schema but return values are described. Contextually complete for the task.

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 coverage is 100%, so the schema already describes parameters. The description does not add parameter-specific details beyond mentioning 'días de baja' implicitly. 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?

The description clearly states the tool calculates sick leave subsidy for employees, specifies two types (common contingency and occupational accident) with exact percentage formulas, and mentions the return values (daily, monthly, total, loss). This distinguishes it from sibling calculators like calcular_pension_publica or calcular_jubilacion_anticipada.

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 description implies usage for sick leave calculations but does not explicitly discuss when to use this tool versus other calculators in the sibling list. No guidance on prerequisites, limitations, or when not to use it.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation3/5

There are many tools with overlapping domains (e.g., multiple retirement calculators, home buying calculators), but detailed descriptions and explicit guidance on when to use comprehensive vs. specific tools help clarify. However, the sheer number (49) still creates potential confusion for an agent.

Naming Consistency5/5

All tools follow a consistent convention: infinitive verb or noun prefix (calcular, comparar, consulta) followed by descriptive noun phrase in snake_case. No mixed styles or irregularities.

Tool Count3/5

49 tools is high but justifiable given the broad scope of Spanish financial/legal calculations. It leans toward the heavy side but remains within a manageable range for a comprehensive server.

Completeness4/5

The tool set covers a wide spectrum of personal finance: income, taxes, housing, inheritance, self-employment, investments, etc. Only minor gaps exist (e.g., no separate tool for rental income beyond the alquiler tools, but included in IRPF).

Resources