Skip to main content
Glama

Aurio Calculators

Estimar la Renta

estimar_renta
Read-onlyIdempotent

Estima la declaración de la Renta (IRPF) de un asalariado en España: si sale a pagar o a devolver y cuánto. Admite comunidad autónoma, hijos, plan de pensiones y, además, rendimientos de autónomo. Úsala para “cuánto me devuelve Hacienda”, “me sale a pagar la Renta”, “cuánto pago de IRPF con 30.000 € brutos”. Si el usuario no sabe sus cotizaciones o retenciones, omítelas (el resultado lo indica). English: Spanish annual income tax return estimate (refund or amount due) for employees.

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": {
      "brutoAnual": "<brutoAnual>"
    },
    "name": "estimar_renta"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccaaNoComunidad autónoma de residencia (foral = País Vasco/Navarra, fuera del cálculo). Region.
hijosNoAños de nacimiento de los hijos que conviven contigo. Children birth years.
brutoAnualYesSalario bruto anual en euros (certificado de retenciones o nóminas). Gross annual salary in EUR.
retencionesNoRetenciones de IRPF ya practicadas en el año, en euros. Tax withheld in EUR.
planPensionesNoAportación anual a un plan de pensiones individual, en euros. Pension plan contribution in EUR.
anioNacimientoNoAño de nacimiento. Birth year.
seguridadSocialNoCotizaciones a la Seguridad Social del trabajador en el año, en euros (vienen en la nómina). Si no se sabe, omitir. Employee social security in EUR.
pagosFraccionados130NoSolo autónomos: pagos fraccionados del modelo 130 ya hechos en el año, en euros.
rendimientoNetoActividadNoSolo autónomos: rendimiento neto anual de la actividad (ingresos − gastos − 5 % de difícil justificación), en euros. Self-employed net income in EUR.

Output Schema

NameRequiredDescriptionDefault
ctaYes
kindYes
foralYes
avisosNo
importeNo
ejercicioYes
resultadoNo
disclaimerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral detail: missing cotizaciones/retenciones can be omitted and the result flags this. Beyond that it says nothing about accuracy limits, assumptions (e.g., no other income, regional tax rules), or how the "foral" region is handled, which matters for an estimator.

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?

Front-loaded with the core purpose, followed by supported inputs, then example queries, then the omission rule – a sensible order. The trailing English sentence largely duplicates the Spanish text for the same agent audience, which is mild waste but not disruptive.

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 an output schema present, return values need not be explained, and the 9 parameters are fully documented in the schema, so the description is nearly sufficient. Remaining gaps are small: no statement of estimation accuracy/disclaimer and no mention that foral regions fall outside the calculation.

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?

With 100% schema description coverage the baseline is 3, and the description earns one step above it by summarizing the optional axes (region, children, pension plan, self-employed net income) and by explicitly telling the caller to omit seguridadSocial and retenciones when unknown. It adds no format or unit hints beyond what the schema already states.

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 ("Estima la declaración de la Renta (IRPF)") and names the output consumers care about (amount due vs. refund). It is clear what the tool computes, but it never positions itself against siblings such as calcular_modelo_130, which also touches autónomo income and could be confused with this estimate.

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?

It supplies concrete trigger phrases ("cuánto me devuelve Hacienda", "me sale a pagar", "cuánto pago de IRPF con 30.000 € brutos") that map user intent to this tool, plus an operating rule to omit unknown social security/withholding figures. It stops short of stating when NOT to use it or naming an alternative tool for the autónomo-only case.

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