Skip to main content
Glama

Delegum

by com.delegum

calcular_reduccion_jornada

Read-only

Calcula el impacto económico de una reducción de jornada por guarda legal (cuidado de hijo menor de 12 años, familiar dependiente o hijo con discapacidad grave). La reducción permitida va de 1/8 a 1/2 de la jornada y el salario baja proporcionalmente. Indica el salario reducido, la merma mensual/anual y cómo queda la cotización a la Seguridad Social (los primeros 24 meses se mantiene la base completa).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
motivoYesMotivo de la reducción de jornada
menos_de_24_mesesNo¿Lleva menos de 24 meses en reducción? (en ese tramo la cotización SS se mantiene a base completa). Por defecto true.
fraccion_reduccionYesFracción de reducción (entre 0 y 1). Ej: 0,5 = media jornada; 0,125 = 1/8
horas_semanales_completasYesHoras semanales a jornada completa según contrato
salario_bruto_mensual_completoYesSalario bruto mensual a jornada completa (€)

TDQS

A4.5/5.0
Behavior4/5

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

The description adds behavioral context beyond the readOnlyHint annotation by explaining that the first 24 months maintain full Social Security contributions. It also states that salary decreases proportionally. This improves transparency for a calculation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a concise three-sentence paragraph. It front-loads the purpose, then provides key constraints, and finally lists outputs. Every sentence is informative with no redundancy.

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?

For a calculation tool with 5 parameters and no output schema, the description provides a good overview of outputs (reduced salary, monthly/annual decrease, Social Security impact). It could be slightly more detailed about the output format, but it is sufficient for an agent to understand the tool's value.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All parameters have schema descriptions (100% coverage). The description adds value by explaining the allowed reduction fraction range (1/8 to 1/2), the significance of the 'menos_de_24_meses' parameter, and the overall logic of proportional salary reduction. It goes beyond the schema.

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 identifies the tool's purpose: calculating the economic impact of a workday reduction for legal custody. It specifies the allowed reduction range (1/8 to 1/2) and the types of situations covered (child under 12, dependent family, disabled child). This distinguishes it from sibling calculation tools.

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 description states when to use the tool (for legal custody reduction) and the eligible reasons. It does not explicitly exclude other cases or mention alternatives, but the context of sibling tools implies it is specific to this scenario. The guidance is clear enough.

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