Skip to main content
Glama

Validate Mexican RFC (SAT)

mx_rfc
Read-onlyIdempotent

Validate a Mexican RFC tax ID (persona física or moral): format, embedded date, homoclave and SAT check digit. Offline; does not query SAT. 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/rfc.

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_rfc"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesRFC (12 or 13 chars). Spaces, dashes and lowercase are normalized.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that the tool is offline and does not query SAT, which confirms behavior consistent with openWorldHint=false. It also exposes important operational details: pricing, Base/x402 payment via _meta['x402/payment'], no charge for failed calls, and an HTTP equivalent endpoint. This is exactly the kind of context an agent needs for a paid validation call.

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 description is front-loaded with the purpose and checks, then moves efficiently through offline behavior, payment mechanics, and the HTTP equivalent. Every sentence carries useful information for invoking the tool, with no filler.

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 simple single-parameter validation tool with rich annotations and a 100%-covered schema, the description covers purpose, connectivity, payment, and endpoint details well. The main remaining gap is that it does not describe the return shape or what a successful validation response contains, which matters because there is no output schema.

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%, and the single value parameter is already documented as a 12- or 13-character RFC with spaces, dashes, and lowercase normalized. The description adds the validation checks performed, but that is not meaningfully additional parameter guidance beyond the schema. Baseline 3 is appropriate 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: validate a Mexican RFC tax ID, with explicit scope covering persona física or moral and the checks performed. An agent can distinguish this from sibling validators such as mx_curp or mx_clabe because the resource is named precisely as RFC.

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 use case is clear from the opening sentence: use this when validating an RFC. The description also states that validation is offline and does not query SAT, which is useful context for choosing it. It does not explicitly name alternatives or when-not-to-use cases, but no same-task alternative is evident from the definition.

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