Skip to main content
Glama

Read and verify a Constancia de Situación Fiscal

csf_verify
Read-only

Read and verify a Constancia de Situación Fiscal. 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/csf-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": "csf_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
qrNoThe text of a QR code printed on the constancia (a siat.sat.gob.mx validadorqr URL), or an array with both. The first-page QR returns the taxpayer; the seal QR returns the issue date.
rfcNoThe taxpayer's RFC.
fileNoThe constancia as base64: the PDF SAT generated, or a PNG or JPEG image of it. A `data:` URL prefix is accepted. Up to 8 MB.
id_cifNoThe idCIF printed under the taxpayer's name on the constancia's first page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint, but the description adds facts the agent could not infer: the call is a live external registry query and is billed to the connected account, with cost delegated to get_account. That billing disclosure is the operationally critical behavior for an agent deciding whether to call it. It does not cover failure or timeout behavior for an external dependency, so it is not a 5.

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 core purpose is front-loaded in the first sentence, followed by the billing warning and the identifier constraint. The trailing 'Details: read_doc "rfc/endpoints/csf-verify"' is terse to the point of being cryptic, but no sentence is padded.

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?

With 100% schema coverage and no output schema, the description covers the essentials an agent needs: what document, that it is a real billed lookup, and what to pass. It is slightly thin on what a successful verification returns (validity status, taxpayer data), which matters for a tool named 'verify' with 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%, so the schema already explains qr, rfc, file and id_cif in detail, including the 8 MB limit and the data: URL prefix. The description adds no meaning beyond that — its only relevant statement, 'Only send identifiers the user gave you,' is a safety rule rather than parameter semantics. Baseline 3 applies when the schema carries the load.

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 states a specific verb and resource: reading and verifying a Constancia de Situación Fiscal. That document type is distinct from the CFDI, CFE, INE and RFC tools, so an agent can tell which document this targets. It stops short of naming a sibling it is not, so it lands at 4 rather than 5.

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

Usage Guidelines3/5

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

It gives real usage context: the call hits the government registry and is billed, and it tells the agent to route cost questions to get_account. It also imposes the constraint 'Only send identifiers the user gave you.' However, it never says when to choose this over rfc_verify, rfc_validate or cfdi_verify, so the selection guidance is only implied.

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