Skip to main content
Glama
Sign In

Delegum

by com.delegum
OverviewDiscussionsAdmin

calcular_excedencia

Read-only

Calcula los derechos y el coste de una excedencia laboral: voluntaria (4 meses–5 años, sin reserva de puesto ni cotización), forzosa, cuidado de hijo (máx. 3 años, primer año con reserva de puesto y cómputo a la SS) o cuidado de familiar (máx. 2 años). Indica la reserva de puesto, los meses que computan para la Seguridad Social y el coste total en ingresos no percibidos.

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": {
      "tipo": "<tipo>",
      "antiguedad_anios": "<antiguedad_anios>",
      "salario_bruto_mensual": "<salario_bruto_mensual>",
      "duracion_meses": "<duracion_meses>"
    },
    "name": "calcular_excedencia"
  }
}

Input Schema

NameRequiredDescriptionDefault
edadNoEdad del trabajador (orienta sobre el impacto en la jubilación). Por defecto 35.
tipoYesTipo de excedencia
duracion_mesesYesDuración solicitada de la excedencia (meses)
antiguedad_aniosYesAntigüedad del trabajador en la empresa (años)
salario_bruto_mensualYesSalario bruto mensual actual (€)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 specifying the outputs (reserva de puesto, meses que computan a la SS, coste total). It does not contradict annotations and provides useful details about each leave type's characteristics.

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 single, well-structured paragraph that front-loads the main purpose and efficiently delivers all necessary information without redundancy. Every sentence adds value.

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?

Despite the absence of an output schema, the description adequately explains the return values (reserva de puesto, meses que computan a la SS, coste total) and covers the tool's scope. It is complete for a calculation tool with 5 parameters and no nested objects.

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%, but the description adds meaning by explaining that 'voluntaria' has restrictions (4 meses–5 años, sin reserva) and that 'cuidado de hijo' includes primer año con reserva. This goes beyond the schema's brief 'Tipo de excedencia' and 'Edad' descriptions.

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 it calculates rights and costs of a labor leave (excedencia), listing specific types (voluntaria, forzosa, cuidado de hijo, cuidado de familiar) with their constraints. This distinguishes it from sibling tools like calcular_reduccion_jornada or calcular_prestacion_maternidad_paternidad.

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 provides clear context by detailing the types of leaves and what the tool outputs, but does not explicitly mention when to use it versus alternatives or specify exclusions. The context is sufficient for an agent to infer usage, but lacks explicit guidance.

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