Skip to main content
Glama

Cuadre — crypto invoicing and on-chain reconciliation

receipt_url

Devuelve la URL del recibo en PDF (con hash, red y valor fiat del arribo) de una factura pagada.

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": {
      "id": "<id>"
    },
    "name": "receipt_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID de la factura

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It usefully reveals the return artifact (a PDF receipt URL containing hash, network and fiat arrival value) and the paid-invoice precondition, but says nothing about authorization requirements, whether the URL is public/temporary/persistent, or the failure mode for unpaid invoices.

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?

One dense, front-loaded sentence with no filler; the resource and its scope appear before the parenthetical enrichment. Nothing could be trimmed without losing information.

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 one-parameter read tool with a fully documented schema and no output schema, the description covers what is returned (a PDF receipt URL) and the key precondition. Only the unpaid-invoice and URL-lifetime behaviors are left unstated.

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?

A single 'id' parameter with 100% schema description coverage ('ID de la factura'), so the schema already does the work. The description adds the implicit constraint that the id must belong to a paid invoice, which is mild added meaning but nothing about accepted id formats.

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 (Devuelve) and a concrete resource (la URL del recibo en PDF) scoped to 'una factura pagada', which distinguishes it in substance from get_invoice, though it never names that sibling explicitly. The parenthetical detail about what the PDF contains (hash, red, valor fiat del arribo) sharpens the purpose further.

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?

Usage is implied by 'de una factura pagada' – the agent can infer this only applies to invoices already paid. However there is no explicit when-to-use vs get_invoice, no statement about what happens if the invoice is unpaid, and no prerequisites or alternatives named.

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