Skip to main content
Glama

Look up a CURP in RENAPO

curp_lookup
Read-only

Look up a CURP in RENAPO. 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 "curp/endpoints/curp-lookup".

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": {
      "curp": "<curp>"
    },
    "name": "curp_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
curpYesThe CURP (18 characters, any case)
include_pdfNoInclude the official PDF as pdf_base64 at no extra credit cost.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds genuinely new behavioral facts, notably that the call hits a real government registry, that it is billed to the connected account, and that costs should be checked via get_account. The privacy constraint on identifiers and the read_doc pointer for endpoint details are also useful. It stops short of stating latency, failure modes, or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short and front-loaded: purpose first, then billing pointer, then the safety constraint, then a documentation reference. Every sentence carries a distinct, actionable fact with no repetition of the name or title.

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?

For a two-parameter read with no output schema, the description covers the important unknowns: real external call, billing impact, identifier provenance, and where to find full endpoint details. It omits any indication of what the lookup returns, which for a registry query with no output schema is a modest gap.

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%, with both curp and include_pdf documented, so the baseline is 3. The description's only added parameter meaning is that include_pdf carries 'no extra credit cost,' a genuinely useful billing detail, but the main parameter receives no elaboration beyond the schema.

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?

'Look up a CURP in RENAPO' pairs a specific verb with a specific resource and registry. 'Asks the government registry for real' signals an authoritative live query rather than a cached/indexed one, which implicitly distinguishes it from curp_search, but neither that sibling nor curp_verify is named, so differentiation is only inferential.

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?

Usage context is implied rather than stated: the caller learns it is a billed live lookup and that identifiers must come from the user ('Only send identifiers the user gave you'). There is no explicit when-to-use / when-not guidance relative to curp_search, curp_verify, or ine_verify, so the agent must infer the choice.

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