Skip to main content
Glama

Full RFC validation (cert lookup + zip search + lists)

rfc_validate
Read-only

Full RFC validation (cert lookup + zip search + lists). 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 "rfc/endpoints/validate".

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": {
      "rfc": "<rfc>"
    },
    "name": "rfc_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
rfcYesThe RFC number to validate (12 or 13 characters)
nameNoOptional. When provided, cert lookup and zip search run in parallel (6–10 s instead of 7–11 s) and a zip is recovered even when the RFC has zero CSDs. Registered taxpayer name as it appears in SAT. **Companies:** omit legal-entity suffixes (S.A. de C.V., SAPI de C.V., SOFOM, AC, SC, etc.). **Persons:** legal name with no honorifics. See top-level `Names` section.
include_curpNoEnable RENAPO identity lookup for the taxpayer or legal representative when a CURP is available. Adds 5 credits to the request (15 total, $0.225 USD pay-as-you-go).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint, openWorldHint), and the description adds genuinely new behavior: this call hits a real government registry and is billed to the connected account, with get_account named as the cost source. The privacy constraint on identifiers is also behaviorally meaningful. It stops short of describing latency, error modes, or partial-result behavior.

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?

Four terse sentences, front-loaded with purpose and billing, with no filler. The trailing pointer to read_doc is compact and useful, though the parenthetical restating the title's sub-operations is slightly redundant.

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 3-parameter, annotation-covered read tool this is largely complete: purpose, cost source, privacy constraint, and a documentation pointer are all present. There is no output schema, and the description only hints at return shape via 'cert lookup + zip search + lists' before deferring to read_doc.

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%, including the performance tradeoff for 'name' and the credit cost of 'include_curp', so the schema already carries the parameter meaning. The description adds nothing about parameters, which is the expected baseline-3 case when the schema does the heavy lifting.

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 ('Full RFC validation') and enumerates the three sub-operations it performs (cert lookup, zip search, lists), so an agent knows exactly what work happens. It does not distinguish itself from near-name siblings such as rfc_verify or rfc_profile, which keeps it below a 5.

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 a concrete usage guardrail ('Only send identifiers the user gave you') and routes the cost question to get_account, but never states when to choose this over rfc_verify, rfc_profile, or the narrower curp_lookup/geo_zip_search siblings. Usage context is implied by the word 'Full' 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