Skip to main content
Glama

Find the SAT-registered zip for a known RFC + name

rfc_find_zip
Read-only

Find the SAT-registered zip for a known RFC + name. 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/find-zip".

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": "<name>"
    },
    "name": "rfc_find_zip"
  }
}

Input Schema

NameRequiredDescriptionDefault
rfcYesThe RFC number to validate (12 or 13 characters)
nameYesRegistered 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 already cover read-only and open-world, and the description adds real value on top: this hits the live government registry, it is billable to the connected account, and there is a privacy constraint on inputs. It does not say what happens on a miss or whether repeat calls are cached/re-billed.

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 purpose, then cost, then pointer. Nothing is wasted, though the opening sentence largely restates the title and the doc pointer could be merged with the cost pointer.

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?

For a two-param external lookup with no output schema, the description never indicates what comes back (just a zip, or zip plus registry metadata) or how a no-match case presents. Cost, privacy and live-call behavior are covered, so the gap is narrow but real.

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 coverage is 100% and the schema already explains length for rfc and the legal-suffix rules for name, so the description adds nothing parameter-specific beyond 'known'. Baseline 3 applies when the schema carries the semantics.

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 concrete verb ('Find') and a concrete resource ('SAT-registered zip') scoped to two inputs, so it is clearly not the same operation as validate/profile/verify siblings. It stops short of naming a sibling to contrast with, so an agent must infer the boundary from the resource name alone.

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?

It states the precondition ('for a known RFC + name'), adds a data-handling rule ('Only send identifiers the user gave you'), and routes cost questions to get_account and endpoint detail to read_doc. No explicit when-not-to-use case versus rfc_profile or rfc_validate is given.

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