Skip to main content
Glama

Cuadre — crypto invoicing and on-chain reconciliation

create_invoice

Crea una factura de cobro con su propia dirección de depósito (watch-only). Devuelve id, URL pública y la dirección a la que el cliente debe pagar.

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": {
      "amount_usd": "<amount_usd>"
    },
    "name": "create_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDías de validez
chainNoRed de cobro (por defecto base)
tokenNoToken de cobro (por defecto USDC)
amount_usdYesMonto de la factura en dólares
client_nameNoNombre del cliente que paga
descriptionNoConcepto de la factura

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / lang
      Removed value: -{
      -  "description": "Idioma de la página pública y del recibo PDF (por defecto: según el navegador del cliente)",
      -  "enum": [
      -    "es",
      -    "en"
      -  ],
      -  "type": "string"
      -}
  2. Changed1 schema field changed
    • addedInput schema / properties / lang
      Added value: +{
      +  "description": "Idioma de la página pública y del recibo PDF (por defecto: según el navegador del cliente)",
      +  "enum": [
      +    "es",
      +    "en"
      +  ],
      +  "type": "string"
      +}
  3. First observed

TDQS

B3.4/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 burden. It does disclose meaningful behavior: a per-invoice watch-only deposit address (no spending capability) and the returned identifiers. It omits auth requirements, whether invoices are persistent/idempotent, and what happens after the validity period (the 'days' parameter hints at expiry but is never explained).

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?

Two sentences, front-loaded with the creation action, followed by the return contract. No redundant or filler wording; every clause carries 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 creation tool with no annotations and no output schema, the description usefully compensates by enumerating the return payload (id, public URL, deposit address). Parameters are fully covered by the schema. The remaining gap is operational context — auth, idempotency, and expiry semantics — which an agent calling a payment-creating tool would want.

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 every parameter (amount_usd, days, chain, token, client_name, description) is already documented with defaults and enums in the schema. The description adds nothing parameter-specific beyond implying that the amount is what the client pays. Baseline 3 applies.

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 ('Crea') and resource ('factura de cobro') plus a distinguishing detail — the invoice carries its own watch-only deposit address. It also names what comes back (id, public URL, payment address). It does not explicitly contrast with siblings like get_invoice or receipt_url, but the create-vs-retrieve distinction is unambiguous.

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 when-to-use or when-not-to-use guidance, no mention of prerequisites (account, API key, funding), and no routing to alternatives. Usage is only implied by the verb 'Crea' and the phrase 'el cliente debe pagar'.

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