Skip to main content
Glama
Sign In

hexadata-tools

by io.github.4robot
OverviewDiscussionsAdmin

Look up SAT CFDI 4.0 catalogs (Mexico)

lookup_sat_catalog

Use this when you need a value of the Mexican CFDI 4.0 catalogs published by the SAT to issue or validate an electronic invoice: product/service key (c_ClaveProdServ, 52k keys with UNSPSC-style hierarchy and similar words), unit (c_ClaveUnidad), CFDI use (c_UsoCFDI, with the receiver regimes allowed), tax regime (c_RegimenFiscal, natural person / legal entity), payment form and method (c_FormaPago, c_MetodoPago), currency, country, export, tax object, voucher type, relation type, tax, periodicity and month. Key lookups return the description, validity dates and the extra columns of the catalog; Spanish text queries return a deterministic ranking by matched words (no LLM). Offline tables; tableVersion is the date of the SAT workbook.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lookup_sat_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoCatalog key to describe, e.g. "84111506", "H87", "G03", "601", "03", "PUE", "MXN", "USA". Provide key or query.
dateNoDate (YYYY-MM-DD) used to decide whether a key is active; defaults to today (UTC).
itemsNoBatch mode: up to 500 items, each with the same fields as a single call. Omit when validating a single value through the top-level fields.
queryNoSpanish text to search, e.g. "servicios de facturación", "pieza", "honorarios". Provide key or query.
catalogNoCFDI 4.0 catalog: "c_ClaveProdServ" (products/services, 52k keys), "c_ClaveUnidad" (units), "c_UsoCFDI", "c_RegimenFiscal", "c_FormaPago", "c_MetodoPago", "c_Moneda", "c_Pais", "c_Exportacion", "c_ObjetoImp", "c_TipoDeComprobante", "c_TipoRelacion", "c_Impuesto", "c_Periodicidad", "c_Meses". The "c_" prefix is optional.
maxResultsNoMaximum matches returned per query item (1–50, default 10).
includeInactiveNoInclude keys whose validity period has ended or not started yet in query results (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and adds useful behavior: key lookups return descriptions, validity dates, and catalog extra columns; text queries return a deterministic matched-word ranking with no LLM; tables are offline and tableVersion reflects the SAT workbook date. It still does not describe error behavior or batch-response shape, so it is strong but not exhaustive.

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?

The description is front-loaded with the triggering condition and then supplies catalog scope and lookup behavior. It is dense but purposeful; the long catalog enumeration is useful, though the first sentence is somewhat heavy.

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?

For a complex lookup tool with seven parameters and no output schema, the description covers the domain scope, key-vs-query behavior, return information, offline nature, and table versioning. The schema itself documents batch mode, date, maxResults, and inactive handling, so the combined definition is complete enough to invoke correctly.

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 description coverage is 100%, so the baseline is 3 even without extra parameter detail. The description adds meaning by explaining key versus Spanish query usage and by qualifying catalogs such as c_ClaveProdServ hierarchy/similar words and c_UsoCFDI receiver regimes, going beyond the schema's catalog list.

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 uses a specific verb-resource pairing: it looks up values from Mexican CFDI 4.0 catalogs published by the SAT. It enumerates the catalog families so an agent can distinguish this from sibling lookup tools like lookup_hs_code or lookup_postal_code 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?

It clearly states when to use the tool: when issuing or validating an electronic invoice and needing a SAT catalog value. It does not explicitly name alternatives or when not to use it, but the CFDI-specific context is strong enough for correct routing among the sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All hexadata-tools toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources