Skip to main content
Glama

Delegum

by com.delegum

calcular_modelo_303

Read-only

Calcula la autoliquidación trimestral del IVA (Modelo 303) de autónomos y empresas. IVA devengado (repercutido en facturas emitidas) menos IVA soportado deducible (facturas recibidas) = cuota a liquidar. Si es positiva, a ingresar; si es negativa, a compensar (o a devolver en el T4). Acepta bases por tipo (21/10/4%).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
trimestreYesTrimestre de la liquidación: T1 (ene-mar), T2 (abr-jun), T3 (jul-sep), T4 (oct-dic)
base_emitidas_4NoBase imponible de facturas emitidas al 4% (€)
base_emitidas_10NoBase imponible de facturas emitidas al 10% (€)
base_emitidas_21NoBase imponible de facturas emitidas al 21% (€)
base_recibidas_4NoBase imponible de facturas recibidas deducibles al 4% (€)
base_recibidas_10NoBase imponible de facturas recibidas deducibles al 10% (€)
base_recibidas_21NoBase imponible de facturas recibidas deducibles al 21% (€)
compensacion_anteriorNoSaldo a compensar de trimestres anteriores (resultado negativo previo no solicitado a devolver), en euros

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true. The description adds context about the calculation formula and result interpretation (positive means payable, negative means compensation/refund). This is adequate but not extensive.

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?

The description is three sentences, front-loaded with the main purpose, and contains no extraneous information. Every sentence adds value.

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?

Given 8 parameters and no output schema, the description explains the calculation and result interpretation sufficiently. It covers the formula and outcome scenarios, though it could mention that results are returned as numbers.

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 100%, baseline 3. The description adds meaning beyond the schema by explaining the overall VAT calculation logic (IVA devengado minus IVA soportado) and the meaning of positive/negative results, which helps the agent understand how parameters relate.

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 clearly states the tool calculates the quarterly VAT self-assessment (Model 303) for self-employed and companies. It explains the core formula and distinguishes from sibling calculators like calcular_iva or calcular_modelo_130.

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?

The description implies the tool is for quarterly VAT calculations but does not explicitly state when to use it versus alternatives like calcular_iva. No guidance on when not to use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Delegum toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation3/5

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.

Naming Consistency5/5

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.

Tool Count3/5

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.

Completeness4/5

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).

Resources