Skip to main content
Glama

Autónomo en UK: impuestos y Making Tax Digital

calcular_autonomo
Read-onlyIdempotent

Para autónomos (self-employed, sole trader) en UK: beneficio, Income Tax y National Insurance Class 4, cuánto apartar cada mes, payments on account, fechas de pago y desde cuándo te obliga Making Tax Digital for Income Tax (resúmenes trimestrales). Admite tener también un sueldo por nómina o alquileres.

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": {
      "ingresos": "<ingresos>"
    },
    "name": "calcular_autonomo"
  }
}

Input Schema

NameRequiredDescriptionDefault
paisNoDónde vives (para el Income Tax).inglaterra
gastosNoGastos del negocio permitidos al año, en libras.
ingresosYesLo que facturas al año como autónomo (ingresos brutos), en libras.
ano_fiscalNoAño fiscal. Si no se indica, el actual.
sueldo_empleoNoSueldo bruto anual por nómina (PAYE), si además trabajas para una empresa.
otros_ingresosNoOtros ingresos del negocio que no son facturación.
ingresos_alquilerNoIngresos brutos por alquiler de inmuebles, si tienes (cuentan para Making Tax Digital).
trading_allowanceNoUsar la trading allowance de £1,000 en vez de los gastos reales.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, closed-world behavior, so the safety profile is covered. The description adds real scope detail — that it covers payments on account, payment dates, and MTD quarterly summaries — but does not say whether results are estimates, what assumptions apply to Scottish/NI rates, or what the response contains.

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?

A single dense sentence front-loads the audience and scope and then lists covered outputs without filler. It is a run-on list rather than clearly structured clauses, but no sentence is wasted.

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 an 8-parameter calculator with full schema coverage, annotations, and no output schema, the description covers the domain and the reports produced. The remaining gap is that it does not describe result structure or precision, which goes unaddressed because no output schema exists.

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 description coverage is 100%, so the baseline is 3; the description earns an extra point by flagging that the calculation accepts concurrent employment income ('sueldo por nómina') and rental income ('alquileres'), telling the agent these optional parameters materially change the result rather than being ignored.

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 names a specific population (autónomos/self-employed/sole trader in UK) and enumerates the concrete outputs — beneficio, Income Tax, National Insurance Class 4, monthly set-aside, payments on account, payment dates, and MTD for Income Tax obligations. It is clear what the tool computes, though it never uses an explicit verb and separates itself from siblings like calcular_nomina only implicitly through the 'autónomo' scope.

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?

Usage is implied by the target audience statement ('Para autónomos... en UK') and the closing note that employment income or rental income can coexist, but there is no explicit when-to-use/when-not guidance and no named alternative for salaried-only or property-only cases.

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