Skip to main content
Glama

Herramientas de Ecuador · ADVISE.ia

Leer la clave de acceso de un comprobante del SRI

leer_clave_de_acceso_sri
Read-onlyIdempotent

Descompone y revisa la clave de acceso (o número de autorización) de 49 dígitos de un comprobante electrónico del SRI de Ecuador (factura, liquidación de compra, nota de crédito, nota de débito, guía de remisión o retención): fecha de emisión, tipo de comprobante, RUC del emisor, ambiente (pruebas o producción), serie, secuencial, código numérico, tipo de emisión y dígito verificador con el módulo 11 de la ficha técnica del SRI. Úsala cuando alguien pegue una clave de acceso o pregunte qué significa. No consulta si el comprobante está autorizado: eso lo dice el SRI.

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": {
      "clave_de_acceso": "<clave_de_acceso>"
    },
    "name": "leer_clave_de_acceso_sri"
  }
}

Input Schema

NameRequiredDescriptionDefault
clave_de_accesoYesLos 49 dígitos de la clave de acceso, tal como aparecen en el RIDE o en el XML (puede traer espacios).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 safety is covered; the description adds real value on top by describing exactly what is decomposed and that the check digit is validated with the módulo 11 rule from the SRI technical sheet. The explicit non-capability (does not verify authorization) is a useful behavioral boundary not present in any structured field. It does not describe output formatting or error behavior for malformed keys, which keeps it from a 5.

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?

Front-loaded with the verb and resource, followed by a compact enumeration of the returned fields and two short usage/exclusion sentences; nearly every clause earns its place. The field list is dense but serves a real purpose since there is no output schema.

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?

With no output schema, the description carries the burden of explaining return values and does so by listing every decomposed field including the verified check digit. It also flags the key limitation (authorization is not checked), so an agent has everything needed to call it and interpret the result.

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?

There is a single parameter with 100% schema description coverage, so the baseline is 3 and the schema already documents the format and space tolerance. The description reinforces the 49-digit constraint and the provenance of the key (RIDE or XML), but adds no validation rules, accepted variants, or failure modes beyond that.

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 ("Descompone y revisa la clave de acceso ... de 49 dígitos") and immediately enumerates the exact outputs: fecha de emisión, tipo de comprobante, RUC del emisor, ambiente, serie, secuencial, código numérico, tipo de emisión y dígito verificador. It also names the covered document types, which removes ambiguity about scope. An agent can distinguish this from the sibling calculators without inspecting the schema.

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 an explicit trigger ("Úsala cuando alguien pegue una clave de acceso o pregunte qué significa") plus an explicit exclusion ("No consulta si el comprobante está autorizado: eso lo dice el SRI"), which prevents a false expectation about authorization status. No sibling tool is named as an alternative, so it falls one step 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