Calcula el IVA español (21%, 10%, 4% o 0%). Puede añadir IVA a una base o extraer la base de un precio con IVA incluido.
| Name | Required | Description | Default |
|---|---|---|---|
| modo | Yes | "anadir" = el importe es la base sin IVA. "quitar" = el importe ya incluye IVA. | |
| importe | Yes | Importe en euros sobre el que operar | |
| tipo_iva | Yes | Tipo: 21, 10, 4 o 0 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotation 'readOnlyHint: true' already covers the read-only nature of the tool. The description adds minimal behavioral context beyond what is in the annotations and schema, but it does not contradict them. It accurately describes the operation without additional disclosures (e.g., side effects or limits).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, consisting of two sentences that front-load the core purpose and actions. Every word is essential, and no irrelevant information is included.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (3 params, no output schema, read-only), the description adequately covers the functionality. It defines the scope (IVA español, specific rates, two modes). While it does not explicitly mention the return value or error conditions, the context (calculation tool) makes this acceptable.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already provides 100% coverage with descriptions for all parameters. The description adds a high-level context ('añadir IVA a una base o extraer la base') but does not provide new details beyond the schema. With full schema coverage, a score of 3 is appropriate as per guidelines.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool calculates Spanish VAT (IVA) with specific rates (21%, 10%, 4%, 0%) and the two modes (add or extract). It uses a specific verb ('calcula') and resource ('IVA español'), distinguishing it from sibling tools which cover other financial calculations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explains when to use each mode ('añadir IVA a una base' or 'extraer la base de un precio con IVA incluido'), providing clear context. However, it does not explicitly state when not to use the tool or mention alternatives, though the context of sibling tools makes this less critical.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
There are many tools with overlapping domains (e.g., multiple retirement calculators, home buying calculators), but detailed descriptions and explicit guidance on when to use comprehensive vs. specific tools help clarify. However, the sheer number (49) still creates potential confusion for an agent.
All tools follow a consistent convention: infinitive verb or noun prefix (calcular, comparar, consulta) followed by descriptive noun phrase in snake_case. No mixed styles or irregularities.
49 tools is high but justifiable given the broad scope of Spanish financial/legal calculations. It leans toward the heavy side but remains within a manageable range for a comprehensive server.
The tool set covers a wide spectrum of personal finance: income, taxes, housing, inheritance, self-employment, investments, etc. Only minor gaps exist (e.g., no separate tool for rental income beyond the alquiler tools, but included in IRPF).
