Skip to main content
Glama

Validate Mexican CURP (RENAPO)

mx_curp
Read-onlyIdempotent

Validate a Mexican CURP: format, birth date, sex, state code, internal consonants and RENAPO check digit. Offline; does not query RENAPO. Price: 0.01 USDC per successful call on Base via x402 (pass the signed payment in _meta['x402/payment']; failed calls are not charged). HTTP equivalent: POST https://json-canon-x402.fly.dev/v1/mx/curp.

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": {
      "value": "<value>"
    },
    "name": "mx_curp"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesCURP (18 chars). Spaces, dashes and lowercase are normalized.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description goes beyond them with operationally critical facts: the call is offline, costs 0.01 USDC per successful call on Base via x402, payment must be passed in _meta['x402/payment'], failed calls are free, and an HTTP equivalent exists. Only the shape of the validation result is left undisclosed.

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 purpose and checks, then the offline caveat, then billing and the HTTP equivalent, so every clause carries information. It is dense and slightly run-on, but no sentence is expendable.

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 one-parameter validator it covers identity, offline scope, payment mechanics, and failure billing. The one real gap is the absence of an output schema combined with no statement of what a result contains (boolean vs. per-check error details), which an agent would want before calling.

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 coverage, and the schema already documents the 18-character format, the example, and normalization of spaces, dashes and lowercase. The description adds nothing parameter-specific, so the baseline of 3 applies.

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 and resource ('Validate a Mexican CURP') and enumerates exactly what is checked: format, birth date, sex, state code, internal consonants, and RENAPO check digit. An agent can distinguish this from mx_rfc or mx_clabe purely from the description.

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 is implied by the resource name and the enumeration of checks, and 'Offline; does not query RENAPO' usefully rules out one wrong expectation. However, no sibling alternatives are named and there is no explicit statement of when an agent should pick this over mx_rfc or a generic validate_json call.

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