Skip to main content
Glama

Estimar cuota de autónomos

kuotia_estimate_reta
Read-onlyIdempotent

Use this when someone asks how much cuota de autónomos (RETA, Seguridad Social) they would pay in Spain, or which tramo applies, from expected yearly income and expenses. Assumes a full year of activity as a persona física autónoma (not societario) in estimación directa simplificada of the common IRPF, income and expenses without recoverable VAT and without their own cuota, the 5 % allowance for gastos de difícil justificación (at most 2,000 EUR a year) and then the general 7 % deduction for generic expenses. The tramo table is the same in all of Spain, but the rendimiento is computed with these common-regime rules: under módulos, estimación directa normal or the foral IRPF of País Vasco and Navarra the tramo may differ. Does not decide whether they qualify for the tarifa plana. Do not use for employees, for companies or for a connected client's real payments.

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": {
      "year": "<year>",
      "annual_income": "<annual_income>",
      "annual_expenses": "<annual_expenses>"
    },
    "name": "kuotia_estimate_reta"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
annual_incomeYes
annual_expensesYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare a read-only, idempotent, closed-world estimate, so the bar is lower, yet the description adds substantial modeling context the agent could not infer: full-year activity, estimación directa simplificada of the common IRPF, amounts excluding recoverable VAT and the autónomo's own cuota, the 5% gastos de difícil justificación cap of 2,000 EUR, and the subsequent 7% generic-expense deduction. It also discloses the key limitation that the tramo table is uniform across Spain while the rendimiento calculation is regime-dependent, which tells the agent when the estimate will not hold.

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?

The trigger is front-loaded in the first clause, followed by the assumption chain and then the exclusions, which is the right order for an agent. The middle is a dense run-on of accounting rules that would read better as a short list, but no sentence is filler — each constraint changes how the result should be interpreted or reported.

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?

For a tax-estimation tool this is close to complete: assumptions, regime caveats, and scope exclusions are all stated, and an output schema exists so return values need no explanation. The only real gap is the unexplained year parameter and the absence of any note on whether results are stable across the 2025 and 2026 tramo tables.

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 0% across three parameters, so the description must carry the load, and it largely does: it defines the expected basis for annual_income and annual_expenses (no recoverable VAT, no own cuota, full year). The year parameter (enum 2025/2026) is never explained in the description, leaving the agent to guess why the year matters to the tramo table.

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 and resource ("Estimar cuota de autónomos (RETA, Seguridad Social)") plus the two outputs the agent gets: the amount payable and which tramo applies. The scope is narrowed to Spain, persona física, and a full year of activity, so it is clearly distinguishable from a net-income estimator or a gestoría workflow tool.

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?

Opens with an explicit trigger ("Use this when someone asks how much cuota... or which tramo applies") and gives concrete exclusions: not for employees, not for companies, not for a connected client's real payments, and it does not decide tarifa plana eligibility. It also warns that under módulos, estimación directa normal, or the foral regimes of País Vasco and Navarra the tramo may differ. It does not name a sibling for the adjacent net-income question, which keeps it short of a full 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