Skip to main content
Glama

Aurio Calculators

Calcular el modelo 130

calcular_modelo_130
Read-onlyIdempotent

Calcula el pago fraccionado de IRPF de un autónomo (tipo modelo 130): 20 % del rendimiento neto acumulado menos retenciones y pagos previos. Úsala para “cuánto pago en el 130”, “pago fraccionado de IRPF este trimestre”. English: Spanish self-employed quarterly income tax prepayment (form 130).

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": {
      "ingresosAcumulados": "<ingresosAcumulados>",
      "gastosAcumulados": "<gastosAcumulados>"
    },
    "name": "calcular_modelo_130"
  }
}

Input Schema

NameRequiredDescriptionDefault
retencionesNoRetenciones de IRPF que te han practicado en facturas, acumuladas, en euros.
pagosPreviosNoPagos fraccionados (130) de trimestres anteriores del mismo año, en euros.
simplificadaNoEstimación directa simplificada (la habitual; aplica el 5 % de gastos de difícil justificación). Por defecto true.
gastosAcumuladosYesGastos deducibles acumulados del año (sin IVA), en euros, incluida la cuota de autónomos. YTD expenses in EUR.
ingresosAcumuladosYesIngresos del año acumulados hasta el trimestre (sin IVA), en euros. YTD income in EUR.

Output Schema

NameRequiredDescriptionDefault
ctaYes
baseYes
kindYes
disclaimerYes
pagoFraccionadoYes
rendimientoNetoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description adds the actual calculation logic applied to the inputs, which is meaningful behavioral context beyond the annotations. It does not mention the 5 % de difícil justificación treatment implied by the simplificada flag, leaving a small gap.

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-loads the verb, the resource and the formula in one sentence, then adds query triggers. The trailing English gloss is a deliberate disambiguation aid rather than filler, though it is slightly redundant for a Spanish-language tool.

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 no explanation; annotations cover the safety profile and the schema fully documents inputs. The description supplies purpose, formula and triggers, which is sufficient to call the tool correctly, with only the simplificada deduction nuance left to the schema.

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 description coverage is 100 %, so all five parameters are already documented in the schema. The description only references retenciones, pagos previos and the net-yield notion implicitly; it adds no format, default or edge-case semantics beyond what the schema provides, so baseline 3 applies.

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?

States a specific verb (calcula) and a specific resource (pago fraccionado de IRPF, modelo 130), and even exposes the computation rule — 20 % del rendimiento neto acumulado menos retenciones y pagos previos — which distinguishes it unambiguously from siblings like calcular_iva_trimestre or estimar_renta.

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?

Provides concrete trigger phrasing ('cuánto pago en el 130', 'pago fraccionado de IRPF este trimestre'), which is strong when-to-use guidance. It stops short of exclusions or naming an alternative sibling (e.g. estimar_renta, calcular_iva_trimestre), so it does not reach a 5.

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