Skip to main content
Glama

Verify a CFDI with SAT

cfdi_verify
Read-only

Verify a CFDI with SAT. 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 "cfdi/endpoints/cfdi-verify".

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

Input Schema

NameRequiredDescriptionDefault
xmlNoThe CFDI XML document as a string, as stamped by the PAC (with its tfd:TimbreFiscalDigital).
uuidNoFolio fiscal (UUID) of the CFDI, any case.
rfc_emisorNoRFC of the issuer (emisor).
rfc_receptorNoRFC of the receiver (receptor).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior5/5

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

Annotations only declare readOnly and openWorld; the description adds two high-stakes facts an agent cannot infer elsewhere: the call hits the real government registry, and it is billed to the connected account, with a pointer to get_account for pricing. For a paid external verification that is exactly the behavior an agent must weigh before invoking.

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?

Four short fragments, with purpose and billing risk front-loaded and the docs pointer last. The telegraphic 'Details: read_doc ...' style is slightly jarring but wastes no words.

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?

All four parameters are optional, yet verification presumably needs either the XML or a UUID plus RFCs, and the description never explains which combination is valid. With no output schema, it also never says what a verification returns (validity, status, registry response), so gaps remain for a billed external call.

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%, so each of xml, uuid, rfc_emisor and rfc_receptor is already documented in the schema, and baseline is 3. The description contributes one real semantic constraint, sourcing values only from the user, but says nothing about how the parameters combine.

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 description names a specific verb ('Verify') and resource ('CFDI') checked against SAT, which separates it from cfe_verify, csf_verify, ine_verify and rfc_verify by the document type being verified. It does not explicitly say how it differs from those sibling verifiers, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no routing to an alternative verifier or to a lookup-based approach. The only constraints given are cost caution and 'only send identifiers the user gave you', which govern how to call it rather than when.

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