Skip to main content
Glama

Verify a voter ID with INE

ine_verify
Read-only

Verify a voter ID with INE. Asks the government registry for real and is billed to the connected account: see get_account for what it costs you. Only send identifiers the user gave you. Details: read_doc "ine/endpoints/ine-verify".

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": {
      "cic": "<cic>"
    },
    "name": "ine_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
cicYesCredential identification code: the nine digits after IDMEX on the first line on the back.
ocrNoOCR, model D. Send this or `id_ciudadano`.
id_ciudadanoNoCitizen identifier, models E to J: the last nine digits of the first line on the back. Send this or `ocr`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnly and open-world behavior, and the description usefully adds that the call hits the real government registry and is billed to the connected account, which is the key operational consequence an agent cannot infer from annotations. It still omits what a failed or ambiguous verification looks like, so it is not fully transparent.

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?

Three short sentences, front-loaded with the purpose, then cost, then a safety constraint and a docs pointer. No filler, though the trailing read_doc pointer is slightly compressed to the point of being cryptic.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should say what a verification returns, and it does not: no mention of a valid/invalid verdict, returned fields, or error behavior. Cost, external-registry behavior, and privacy are covered, leaving the return-value gap as the main shortfall.

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 coverage is 100% and each parameter already explains its model-specific format and the either/or between ocr and id_ciudadano. The description adds only a privacy rule for the identifiers and no format or selection detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Verify a voter ID with INE" gives a specific verb and resource, and the INE/IDMEX framing separates it from the RFC/CFDI/CURP siblings by domain. It stops short of naming an alternative tool for overlapping identity lookups, so an agent still has to reason about which verification to pick.

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?

It contributes one genuine usage constraint, "Only send identifiers the user gave you," and points at get_account for pricing. There is no explicit when-to-use versus when-not, and no routing guidance relative to curp_lookup or the other verify tools, so guidance is implied rather than stated.

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