Skip to main content
Glama

Verify an RFC, optionally against a name + zip

rfc_verify
Read-only

Verify an RFC, optionally against a name + zip. 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/verify".

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

Input Schema

NameRequiredDescriptionDefault
rfcYesThe RFC number to validate (12 or 13 characters)
zipNoOptional. Requires `name`. 5-digit Mexican postal code
nameNoOptional. Requires `zip`. 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations cover readOnly and openWorld, but the description adds two things they cannot: the call hits the live government registry and it is billed to the connected account, with get_account named as the cost source. Reversibility and latency are not mentioned, and the privacy constraint is a useful extra behavioral note.

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, front-loaded with the core action, then cost, then input-hygiene rule, ending in a compact deep-doc pointer. "Asks the government registry for real" is slightly informal but earns its place by signalling a live external call.

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?

With no output schema, the description never indicates what a verification result contains (valid/invalid RFC, name match status, registry status code), leaving the agent unsure how to interpret the response. Parameter and billing context are otherwise adequate for a 3-parameter tool.

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%, so the schema already explains the 12/13-character RFC, the 5-digit zip pattern, and the mutual name/zip dependency. The description restates the optional name+zip pairing without adding format or validation semantics beyond that.

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 first sentence gives a specific verb (verify) and resource (RFC) plus the optional enhancement path (name + zip). It stops short of distinguishing this from the close sibling rfc_validate, so an agent cannot tell from the description alone which one to pick.

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?

"Only send identifiers the user gave you" is a concrete usage constraint, and the cost pointer to get_account tells the agent when to check pricing before calling. There is no explicit when-not-to-use rule or routing to rfc_validate/rfc_profile, which keeps it out of 5 territory.

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