Skip to main content
Glama

Herramientas de Ecuador · ADVISE.ia

Validar RUC o cédula de Ecuador

validar_ruc_o_cedula
Read-onlyIdempotent

Valida una cédula de identidad (10 dígitos) o un RUC (13 dígitos) de Ecuador: código de provincia, tercer dígito (persona natural, sociedad privada o entidad pública), terminación 001 y dígito verificador (módulo 10 para la cédula; módulo 11 para sociedades y entidades públicas). Úsala cuando pregunten si un RUC o una cédula ecuatoriana es válido, de qué tipo es o de qué provincia. Solo revisa el formato: no consulta al SRI ni al Registro Civil, así que no dice a nombre de quién está ni si el RUC está activo.

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": {
      "numero": "<numero>"
    },
    "name": "validar_ruc_o_cedula"
  }
}

Input Schema

NameRequiredDescriptionDefault
numeroYesCédula (10 dígitos) o RUC (13 dígitos). Puede traer espacios o guiones.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already state readOnlyHint, idempotentHint, openWorldHint=false y destructiveHint=false, so the description does not need to restate safety; what it adds is substantive: the checks performed and, crucially, the limits (solo formato, sin consulta al SRI/Registro Civil, sin titular ni estado activo). It does not describe the response shape, which keeps it at 4 rather than 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?

Two dense sentences: the first states what is validated and how, the second states when to use it and what it cannot do, so it is front-loaded and free of filler. It is long, but every clause carries operational meaning for a validation tool; a shorter version would drop the módulo 10/11 detail or the scope limit.

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 single-parameter, read-only validator with no output schema and full annotation coverage, the description supplies everything needed to call it correctly and to interpret the negative result: input formats, what the checks mean, and the explicit boundaries (no titular, no estado). Nothing an agent needs before invoking it or before relaying the answer to a user is missing.

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% and the parameter already documents digits and allowed spaces/hyphens, so the baseline is 3; the description adds meaning beyond that by tying the length to the document type and clarifying that the digits encode provincia, tipo de contribuyente, terminación 001 y dígito verificador, which helps the agent understand what the input carries even though there is only one parameter.

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 names the specific resource (cédula de 10 dígitos o RUC de 13 dígitos de Ecuador) and the exact verb (validar), and it enumerates what is checked: provincia, tercer dígito, terminación 001 y dígito verificador con el módulo aplicable. That is far more than any sibling tool (all calculators/readers of SRI data) offers, so the agent can separate it without opening 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use triggers ("pregunten si un RUC o una cédula ecuatoriana es válido, de qué tipo es o de qué provincia") and explicit exclusions (no consulta al SRI ni al Registro Civil, no dice el titular ni si está activo), which routes the agent away from any SRI-consulting sibling when the question is about the holder rather than the format.

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