Skip to main content
Glama

Cuadre — crypto invoicing and on-chain reconciliation

get_invoice

Consulta el estado de una factura: waiting, partial, paid, over o expired, con monto recibido y valor en dólares al arribo.

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

Input Schema

NameRequiredDescriptionDefault
idYesID de la factura

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does convey that this is a read of invoice state and what the response contains (status, amount received, dollar value at arrival). It does not disclose behavior for missing/invalid invoice IDs, permission requirements, or any side effects, which leaves meaningful gaps for an unannotated tool.

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?

One front-loaded sentence with no filler; the status enumeration earns its place by telling the agent what values to expect. The closing phrase "valor en dólares al arribo" is slightly ambiguous but does not bloat the definition.

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 no output schema, the description covers the essential return information (status values, amount received, dollar value), which compensates for the absent output schema. Only error/edge-case behavior is missing, a minor gap at this complexity level.

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?

The single parameter `id` already has a full schema description ("ID de la factura") at 100% coverage, so the schema does the work. The description adds no format, source, or example for the ID, leaving the baseline score appropriate.

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 ("Consulta el estado de una factura") and even enumerates the possible status values, so the agent knows exactly what it retrieves. It does not explicitly contrast itself with siblings create_invoice or receipt_url, but the read-verb makes the distinction self-evident.

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 only implied: the word "Consulta" signals a read operation, and the enumerated statuses hint at status-checking workflows. There is no explicit when-to-use, when-not-to-use, or routing guidance toward create_invoice or receipt_url, and no prerequisite (e.g., invoice must exist) is stated.

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