Skip to main content
Glama

Check Mexico RFC (tax ID)

validate_mexico_rfc
Read-onlyIdempotent

Check a Mexican RFC (12 characters for companies, 13 for individuals): structure, encoded date and SAT check digit, plus whether it appears on SAT's public lists under article 69-B of the Código Fiscal de la Federación (taxpayers presumed or confirmed to invoice non-existent operations, also called EFOS) and article 69 (not located, unpaid or cancelled tax debts, tax-crime convictions). Returns the list status with publication dates and a review/fail assessment with reasons. Mexico publishes no RFC registry, so the result never confirms that an RFC is registered or active and never returns pass. Company names are returned only when a SAT list carries them; individuals get list status only, without name or birth date.

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": "validate_mexico_rfc"
  }
}

Input Schema

NameRequiredDescriptionDefault
rfcYesMexican RFC, 12 or 13 characters, e.g. "SAT970701NN3". Case, spaces and dashes are ignored.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / rfc / description
      Previous value: -"Mexican RFC, 12 or 13 characters, e.g. \"AAA080808HL8\". Case, spaces and dashes are ignored."New value: +"Mexican RFC, 12 or 13 characters, e.g. \"SAT970701NN3\". Case, spaces and dashes are ignored."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, but the description adds substantial behavior the annotations cannot: results never confirm registration or active status, never return pass, list status carries publication dates, company names appear only if a SAT list carries them, and individuals get list status only (no name or birth date). This corrects a plausible agent misconception that a validator would return a positive confirmation.

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?

A single dense paragraph with no filler sentences; the scope constraint and the key limitation ("never confirms registration... never returns pass") are front-loaded. It is heavy to parse because of the stacked parenthetical legal citations, which costs it a point but no sentence is wasted.

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

Completeness5/5

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

No output schema exists, and the description compensates fully by describing the return payload (list status with publication dates, review/fail assessment with reasons) and the absence of a pass outcome. For a single-parameter tool that is as complete as an agent needs to call and interpret it.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: 12 characters means a company and 13 means an individual, which affects what the result can contain (company names vs list-only for individuals). Format-normalization details (case, spaces, dashes) are already in the schema and correctly not repeated.

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 ("Check a Mexican RFC") plus exactly what is validated: structure, encoded date, SAT check digit, and 69-B/69 list membership. Specific enough that an agent can distinguish it from the sibling country-specific validators (validate_colombia_nit, validate_peru_ruc, etc.) without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The Mexico-specific framing implicitly tells the agent this is the tool for RFCs rather than other tax IDs, and the explicit "never returns pass" / "no RFC registry" caveats tell the agent when NOT to expect a verification outcome. It stops short of naming a sibling alternative (e.g. validate_tax_id) for non-Mexican input, so it is a 4 rather than a 5.

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