Skip to main content
Glama

Guía de autónomos

kuotia_get_autonomo_guide
Read-onlyIdempotent

Use this when someone asks how to become autónomo in Spain (alta in Hacienda with modelo 036 and in the RETA), what an autónomo files each quarter and year, how IVA, IRPF retención and the cuota de autónomos work, what an invoice must contain, what a gestoría or gestor does, whether an autónomo needs one and what to check when choosing one (topic need_gestoria), or how to change gestoría. Returns short statements, each with its official source and review date. Modelo 037 no longer exists (abolished in February 2025). Do not use for personal legal advice, companies or non-Spanish taxes.

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": {
      "topic": "<topic>"
    },
    "name": "kuotia_get_autonomo_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description adds genuine context beyond them: returns short statements each with an official source and review date, plus a freshness warning that Modelo 037 was abolished in February 2025.

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 usage trigger, and the long enumeration earns its length by defining the topic enum. The parenthetical 'topic need_gestoria' and the trailing exclusions are well placed, though the single run-on sentence is dense.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter, read-only knowledge tool with an output schema, the definition supplies scope, topic meanings, source/review-date behavior, domain currency note and out-of-scope boundaries. Nothing needed to invoke it correctly is missing.

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 0%, so the description carries the burden, and it largely does: nearly every enum value is glossed in prose (alta = modelo 036 at Hacienda plus RETA registration, quarterly_and_annual_returns, iva, irpf retención, cuota de autónomos, invoices, gestoria, need_gestoria named verbatim, change_gestoria). A couple of values are only implicitly covered, so it is not exhaustive.

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 verb and resource ('how to become autónomo in Spain', quarterly filings, IVA, IRPF, cuota, invoices, gestoría) and enumerates the exact topical scope, so an agent can distinguish it from the sibling estimate/calendar tools 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 gives an explicit trigger ('Use this when someone asks...') and explicit exclusions ('Do not use for personal legal advice, companies or non-Spanish taxes'), which is strong when/when-not guidance. It stops short of naming sibling alternatives such as the RETA or net-income estimators for adjacent questions, so routing is only partially closed.

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