Skip to main content
Glama

Aurio Calculators

Calcular la cuota de autónomos

cuota_autonomos
Read-onlyIdempotent

Calcula la cuota mensual de autónomos (RETA) según el tramo de rendimientos: tramo, base mínima y cuota mínima/máxima. Úsala para “cuánto pago de autónomos”, “cuota de autónomos con 2.000 € al mes”, “qué tramo de autónomos me toca”. English: Spanish self-employed social security fee by income bracket.

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": {
      "rendimientoNetoAnual": "<rendimientoNetoAnual>"
    },
    "name": "cuota_autonomos"
  }
}

Input Schema

NameRequiredDescriptionDefault
societarioNoAutónomo societario (administrador de una sociedad). Por defecto false.
rendimientoNetoAnualYesRendimiento neto anual previsto (ingresos − gastos deducibles, SIN restar la cuota de autónomos), en euros. Expected annual net income in EUR.

Output Schema

NameRequiredDescriptionDefault
ctaYes
anioYes
kindYes
tramoYes
baseMinimaYes
disclaimerYes
cuotaMaximaYes
cuotaMinimaYes

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 establish read-only, idempotent, non-destructive, closed-world behavior, so the description needn't restate safety. It adds domain behavior beyond that: the result is derived from income brackets and reports bracket, minimum base, and min/max contribution. It does not discuss rate year, rounding, or estimation caveats.

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?

Two sentences plus a short English gloss, front-loaded with the calculation. The query examples are useful; the English translation adds little for a Spanish-named tool but is brief.

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, full parameter descriptions, and strong annotation coverage, the description supplies enough context to call the tool correctly. It could be slightly richer on assumptions (rate year, estimate vs official calculation), but the core calculation and return components are covered.

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 coverage is 100% and the schema documents both rendimientoNetoAnual and societario, including annual net income semantics. The description adds only a high-level 'según el tramo de rendimientos' and a monthly example; it does not explain societario or the annual-excluding-quota convention.

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 names a specific calculation (monthly RETA self-employed contribution) and ties it to income brackets, listing the returned components (tramo, base mínima, cuota mínima/máxima). This makes it distinguishable from tax/affordability siblings without opening the schema.

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 Spanish user phrasings ('cuánto pago de autónomos', 'con 2.000 € al mes', 'qué tramo me toca'), which clearly mark the intended use. It does not name when not to use it or point to alternatives such as calcular_modelo_130 or estimar_renta, so it stops short of full routing guidance.

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