Skip to main content
Glama

Herramientas de Ecuador · ADVISE.ia

Vencimientos tributarios del SRI por noveno dígito

vencimientos_tributarios_sri
Read-onlyIdempotent

Fechas de vencimiento de las obligaciones del SRI de Ecuador en un mes, según el noveno dígito del RUC (o la cédula) y el tipo de contribuyente: declaración de IVA mensual o semestral, retenciones en la fuente, ATS, impuesto a la renta (personas naturales en marzo, sociedades en abril, RIMPE en abril o mayo) y anticipo sobre utilidades no distribuidas. Aplica el día por noveno dígito (1 → 10 … 0 → 28), el día 11 de contribuyentes especiales, el día 28 de Galápagos y el traslado al siguiente día hábil por fines de semana y feriados nacionales. Cubre de noviembre de 2026 a diciembre de 2027. Úsala cuando pregunten cuándo vence una declaración o el calendario tributario de un RUC.

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": {
      "ruc_o_noveno_digito": "<ruc_o_noveno_digito>"
    },
    "name": "vencimientos_tributarios_sri"
  }
}

Input Schema

NameRequiredDescriptionDefault
mesNoMes del vencimiento (1 a 12). Rango disponible: noviembre de 2026 a diciembre de 2027. Si falta, el mes actual en Ecuador.
anioNoAño del vencimiento (2026 o 2027). Si falta, el mes actual en Ecuador.
galapagosNotrue si el domicilio principal está en Galápagos (día 28 para IVA, retenciones y renta).
tipo_contribuyenteNoTipo de contribuyente: sociedad = Sociedad (régimen general); pn = Persona natural (régimen general); rimpe-emp-pn = RIMPE emprendedor: persona natural; rimpe-emp-soc = RIMPE emprendedor: sociedad; rimpe-np = RIMPE negocio popular; ce-soc = Contribuyente especial: sociedad; ce-pn = Contribuyente especial: persona natural. Si falta: «pn» cuando el RUC es de persona natural (tercer dígito 0 a 5) y «sociedad» en los demás casos.
ruc_o_noveno_digitoYesRUC (13 dígitos), cédula (10) o solo el noveno dígito (un número de 0 a 9).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered; the description adds substantive domain behavior instead: the ninth-digit-to-day mapping (1→10 … 0→28), day 11 for especiales, day 28 for Galápagos, and business-day shifting for weekends and national holidays. It also bounds coverage to November 2026–December 2027. It does not say what happens when the requested month falls outside that range, nor describe the shape of the returned calendar.

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?

A single dense paragraph that front-loads the core purpose and coverage window before enumerating obligation types and the day-mapping rules. The obligation enumeration earns its place by helping an agent match user phrasing, though the paragraph is long and could be split for readability.

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?

With 5 parameters (1 required), full schema coverage and no output schema, the description supplies the domain rules and validity window an agent needs to call it correctly. The remaining gap is the return shape and out-of-range behavior, which the description leaves unstated and which no output schema covers.

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%: mes, anio, galapagos, tipo_contribuyente defaults and the ruc_o_noveno_digito formats are all documented in the schema itself. The description restates the ninth-digit rule and coverage window, which reinforces rather than adds new parameter-level meaning. Appropriate 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?

States a concrete resource and verb: tax due dates (fechas de vencimiento) for SRI obligations in a given month, keyed to the ninth RUC digit and contributor type. It enumerates the obligation types covered (IVA, retenciones, ATS, renta, anticipo) and the date range, so an agent can tell it apart from siblings like calcular_iva or calcular_retencion_sri that compute amounts rather than dates.

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?

Ends with an explicit trigger: 'Úsala cuando pregunten cuándo vence una declaración o el calendario tributario de un RUC.' That gives clear when-to-use context. It does not name a sibling alternative or state when-not to use it (e.g., for computing the amount owed), 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