Skip to main content
Glama

Find a CURP by personal data

curp_search
Read-only

Find a CURP by personal data. 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-search".

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": {
      "names": "<names>",
      "paternal_surname": "<paternal_surname>",
      "birthdate": "<birthdate>",
      "sex": "<sex>",
      "state": "<state>"
    },
    "name": "curp_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sexYes
namesYes
stateYesTwo-letter state of birth code as used in CURPs (e.g. DF, JC, NL), or NE for people born abroad.
birthdateYes
include_pdfNoInclude the official CURP PDF in pdf_base64 at no extra credit cost. A PDF download failure returns found: null and is not charged.
paternal_surnameYes
mothers_maiden_nameNoOmit when the person has a single surname.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

The annotations only declare readOnlyHint and openWorldHint; the description adds genuinely useful behavior the agent would otherwise miss — the call has a monetary cost billed to the connected account and hits a live external registry. It also adds a privacy directive (only send identifiers the user gave you) and defers deeper detail to read_doc. What it omits is what happens on no-match or failure, which the schema only covers for the PDF case.

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 with the purpose front-loaded, followed by cost and safety caveats. The phrasing 'Asks the government registry for real' is slightly awkward, but no sentence is wasted.

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?

For a 7-parameter, billed, open-world lookup with no output schema, the definition covers cost and data-provenance but leaves the agent guessing about the return shape (single CURP? PDF? partial results?) and about the required fields' semantics. The read_doc pointer partially compensates but is not self-contained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 43%, so the description needs to compensate for undocumented parameters — but it says nothing about names, paternal_surname, birthdate, sex, or state beyond the vague phrase 'personal data'. The only parameter detail present lives in the schema itself (state codes, omitting mother's maiden name, the PDF flag), not in the description.

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?

The description names a specific verb and resource: find a CURP from a person's personal data. That is unambiguous on its own, but it never distinguishes this from the sibling curp_lookup, so an agent cannot tell the two apart from the definition alone.

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 gives real context for when to be careful: the call hits the government registry, is billed to the account, and get_account must be consulted for the price. However, it offers no explicit when-to-use vs. when-not-to-use rule against the alternative CURP tool, and no prerequisites or rate/eligibility conditions.

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