Skip to main content
Glama

Aurio Calculators

Calcular el IVA del trimestre

calcular_iva_trimestre
Read-onlyIdempotent

Calcula el IVA trimestral de un autónomo (tipo modelo 303): IVA repercutido menos IVA soportado deducible. Úsala para “cuánto tengo que pagar de IVA este trimestre”, “calcular el 303”, “IVA a ingresar”. Solo calcula: no presenta nada ante la AEAT. English: quarterly VAT (Spain, form 303) estimate.

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_iva_trimestre"
  }
}

Input Schema

NameRequiredDescriptionDefault
gastosNoGastos/facturas recibidas del trimestre con IVA soportado. Expenses by VAT rate.
ingresosYesVentas/facturas emitidas del trimestre agrupadas por tipo de IVA. Sales by VAT rate.

Output Schema

NameRequiredDescriptionDefault
ctaYes
kindYes
resultadoYes
disclaimerYes
ivaRepercutidoYes
resultadoImporteYes
ivaSoportadoDeducibleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 the safety profile is covered. The description adds genuinely new behavioral context beyond them: it is a pure calculation with no filing side effect, and it is framed as an "estimate" (English gloss) rather than an authoritative return. It does not discuss rounding or how default VAT rates are applied, which the schema partly covers.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the definition and formula, followed by trigger phrases and the scope boundary, all in a few compact clauses with no filler. The one-line English gloss is a useful addition rather than padding.

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 two-parameter, fully described calculation tool with an output schema and rich annotations, the agent has everything needed: what it computes, the formula, when to reach for it, and the fact that it has no external side effects. Return values need not be explained because an output schema exists.

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%, so the schema already documents bases, VAT type enums and deduciblePct in detail. The description's formula clarifies how the two top-level arrays relate to the result, but it adds no per-parameter meaning beyond the schema, so the baseline of 3 applies.

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+resource ("Calcula el IVA trimestral de un autónomo, tipo modelo 303") and gives the exact formula ("IVA repercutido menos IVA soportado deducible"). The explicit "Solo calcula: no presenta nada ante la AEAT" boundary separates it from any filing action and from the sibling tax/estimate tools (modelo 130, renta, ahorro).

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?

Provides concrete trigger phrasings ("cuánto tengo que pagar de IVA este trimestre", "calcular el 303", "IVA a ingresar") so an agent can match user intent. It also excludes presentation to the AEAT, but does not explicitly contrast itself with any sibling tool, so guidance is clear without being a full when/when-not map.

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