Skip to main content
Glama

Calcular nómina en UK

calcular_nomina
Read-onlyIdempotent

Calcula cuánto te queda neto de tu sueldo en Reino Unido (UK take-home pay), anual o por horas: Income Tax por tramos, National Insurance, préstamo de estudiante y pensión, al año y al mes, tipo marginal y aviso si una tarifa por hora está por debajo del salario mínimo. Por año fiscal y país (Inglaterra, Gales, Irlanda del Norte o Escocia). Indica salario_anual, o salario_hora y horas_semana.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calcular_nomina"
  }
}

Input Schema

NameRequiredDescriptionDefault
edadNoOpcional. Para comprobar el salario mínimo por edad (21+, 18-20, menos de 18).
paisNoDónde vives (para el Income Tax). Escocia tiene tramos propios.inglaterra
prestamosNoPréstamos de estudiante de UK: plan1, plan2, plan4 (Escocia), plan5 (desde abril de 2026) y/o postgrado.
ano_fiscalNoAño fiscal (6 de abril a 5 de abril). Si no se indica, el actual.
horas_semanaNoHoras a la semana si cobras por horas, p. ej. 35.
pension_baseNoqualifying: solo lo que ganas entre £6,240 y £50,270 (lo más habitual). todo: todo el salario.qualifying
pension_tipoNonet_pay: antes de impuestos. salary_sacrifice: también baja el NI. relief_at_source: después de impuestos, el proveedor añade el 20%.net_pay
salario_horaNoSi cobras por horas: libras por hora, p. ej. 12.5 (junto con horas_semana).
salario_anualNoSalario bruto anual en libras, p. ej. 30000.
pension_porcentajeNoLo que aportas tú a la pensión de empresa, en %. Con auto-enrolment suele ser 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / edad
      Added value: +{
      +  "description": "Opcional. Para comprobar el salario mínimo por edad (21+, 18-20, menos de 18).",
      +  "maximum": 100,
      +  "minimum": 16,
      +  "type": "integer"
      +}
    • addedInput schema / properties / horas_semana
      Added value: +{
      +  "description": "Horas a la semana si cobras por horas, p. ej. 35.",
      +  "maximum": 80,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / salario_hora
      Added value: +{
      +  "description": "Si cobras por horas: libras por hora, p. ej. 12.5 (junto con horas_semana).",
      +  "minimum": 0,
      +  "type": "number"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "salario_anual"
      -]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds real value by disclosing what the tool returns (neto anual y mensual, tipo marginal) and that it flags hourly rates below the minimum wage. It also bounds behavior by fiscal year and country. It does not state assumptions about tax-code defaults or rounding, which would have pushed it higher.

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?

It is a single dense paragraph that front-loads the outcome (neto anual o por horas) before listing components and then the required inputs. Every clause carries information, though the enumeration of deductions is somewhat compressed and could be split for faster scanning.

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?

With no output schema, the description carries the burden of describing return values and does so (anual y mensual, tipo marginal, aviso de salario mínimo). All 10 parameters are fully documented in the schema, so nothing an agent needs to invoke the tool correctly is missing.

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%, so the baseline is 3; the description earns an extra point because with zero required parameters it clarifies the intended input combinations (salario_anual alone versus salario_hora plus horas_semana) and ties pais/ano_fiscal to the tax rules applied. It adds no syntax or format detail beyond the schema for the remaining parameters such as pension_base or prestamos.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource (calcular el neto del sueldo en UK) and enumerates the components: Income Tax por tramos, National Insurance, préstamo de estudiante, pensión, tipo marginal y aviso de salario mínimo. It clearly differentiates itself from the calculation siblings (ISA, vivienda) by domain, though it never explicitly names an alternative tool.

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?

It states the two valid input modes ('Indica salario_anual, o salario_hora y horas_semana') and the geographic/fiscal-year dimension, which is useful invocation guidance given that no parameter is required. However, there is no explicit when-to-use vs when-not guidance relative to siblings such as comparar_sueldos, so usage is only implied.

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