Skip to main content
Glama

Herramientas de Ecuador · ADVISE.ia

Calcular el IVA en Ecuador (15 % o 0 %)

calcular_iva
Read-onlyIdempotent

Agrega el IVA a un precio o lo separa de un total que ya lo incluye, en Ecuador: tarifa general 15 % (vigente desde el 1 de abril de 2024, Decreto Ejecutivo 198) o tarifa 0 %. Devuelve la base imponible, el IVA y el total redondeados al centavo. Úsala para calcular el IVA, el precio con IVA o la base sin IVA de un valor.

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": {
      "monto": "<monto>"
    },
    "name": "calcular_iva"
  }
}

Input Schema

NameRequiredDescriptionDefault
montoYesMonto en USD: el precio sin IVA (para agregar) o el total con IVA (para quitar).
tarifaNoTarifa de IVA: 15 (general, por defecto) o 0.
operacionNo«agregar» el IVA a un precio (por defecto) o «quitar» el IVA de un total.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare it as a read-only, idempotent, closed-world, non-destructive computation. The description adds useful detail beyond them: it says the result is rounded to the centavo and states which three values are returned, plus the rate in force and its legal basis. It does not discuss input validation edge cases such as large amounts, but that is minor.

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?

Two sentences, front-loaded with the core action and the rate scope, followed by the return values and usage cue. Little is wasted; the parenthetical legal citation is justified because it pins the rate version, though it slightly lengthens the first sentence.

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?

There is no output schema, but the description explicitly names the three returned values and their rounding, so an agent knows what to expect. Combined with the rate scope, defaults, and the two operation modes, the description is complete for a simple three-parameter calculating tool.

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 description coverage is 100 %, so all three parameters are already documented in the schema with their defaults and enums. The description restates the agregar/quitar meaning and the 15 % default, reinforcing them but adding no formatting or constraint detail beyond the schema, which fits the baseline of 3.

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 states a specific verb and resource: it adds IVA to a price or separates it from a total, in Ecuador, at 15 % or 0 %. It also names the legal basis (Decreto Ejecutivo 198) and the effective date, so the agent can tell exactly which computation this tool performs rather than any sibling calculator.

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?

The closing sentence states when to use it: to compute the IVA, the price with IVA, or the pre-IVA base of an amount. It gives clear positive context but no explicit exclusions or alternatives (for example, other tax tools such as retenciones), so it stops short of full routing guidance.

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