Skip to main content
Glama

Verify a CFE electricity receipt

cfe_verify
Read-only

Verify a CFE electricity receipt. 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 "cfe/endpoints/cfe-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": "cfe_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoThe receipt as base64: CFE's PDF, a scan, or a PNG or JPEG photo that shows the payment barcode. A `data:` URL prefix is accepted. Up to 8 MB. Send this, or the three values below.
nameNoThe holder's name exactly as the receipt prints it, cut short if the receipt cuts it short.
totalNoThe amount to pay (Total a pagar) in whole pesos.
service_numberNoThe 12-digit service number (No. de servicio).

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 declare readOnlyHint and openWorldHint, yet the description adds material context beyond them: it hits a real government registry and is billed to the connected account, with a pointer to get_account for pricing. The privacy constraint on identifiers is also non-obvious behavior. Return shape is not described, but no output schema exists and the cost/privacy disclosure is the harder information.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tight sentences with no padding: purpose first, then billing/cost, then the privacy rule, then the docs pointer. Every clause carries an actionable constraint or routing hint.

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?

For a read-only lookup with fully documented parameters and no output schema, the definition covers purpose, cost implications, privacy constraints, and where to find endpoint details. What is missing is minimal: any hint about result contents or failure modes (e.g., invalid receipt, registry timeout).

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%, including the either/or between the base64 file and the three identifier fields, size and format limits, and exact-match semantics for name. The description adds only the generic 'only send identifiers the user gave you' rule, so the schema carries the parameter burden.

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?

States a specific verb and resource ('Verify a CFE electricity receipt'), and the resource name itself separates it from the CFDI/CSF/INE verification siblings. It stops short of explicitly contrasting those alternatives, so it is clear but not fully differentiated.

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?

'Only send identifiers the user gave you' gives a concrete input-restriction rule, and get_account/read_doc are named for cost and details. There is no guidance on when to prefer this over cfdi_verify or csf_verify, or when verification is unnecessary, so usage 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