Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

order_status

State of an order YOU paid (in the database and on chain: no deposit, in escrow, released, refunded, disputed), with the next step. Without ordenId it lists your active ones; the ones your owner pays on the web are not listed here and you cannot move them. The purchase is your owner's: the download and the receipt are theirs, and the download is enabled as soon as the deposit is confirmed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
txHashNoOptional: hash of your fundPurchase transaction, to verify it.
ordenIdNoDEPRECATED alias of `orderId`: it still works, but use `orderId` (it will be removed in a future round, no date yet). The ordenId (uuid) from prepare_payment. Without it, it lists your active orders.
orderIdNoThe ordenId (uuid) from prepare_payment. Without it, it lists your active orders.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
txNoOnly if you sent txHash: the verdict on that transaction. null if you did not send it.
notaNoOnly in the inventory: a text clarification of what the list contains.
walletNoThe buyer wallet of the order.
importeNoOnly in the detail: the amount of the order in both units.
ordenIdNoOnly in the detail: the uuid of the order queried.
ordenesNoOnly in the inventory (call WITHOUT ordenId): your active orders, from the newest to the oldest (max. 20).
anomaliaNoOnly if the database and the chain cannot be reconciled; the team has already been notified.
compraIdNoOnly in the detail: the on-chain identifier (bytes32).
estadoBdNoState according to Bernuvia's database.
finalizadoNoIs the deposit in finalized blocks? null if it could not be determined.
fundTxHashNoHash of the deposit transaction, or null if it is not on record (it can be null even when the order is funded).
notaOnChainNoOnly if the read was skipped: why, and when to come back.
sincronizadoNotrue if this call moved the state in the database to align it with the chain.
depositoVistoNoDoes the chain already show the deposit? If true, do NOT deposit again.
estadoOnChainNoState according to the contract, or null if the read was skipped or failed. "none" = no deposit.
plantillaSlugNoSlug of the template, or null if it no longer exists.
siguientePasoNoOnly in the detail: what to do now, in one sentence.
notaFundTxHashNoOnly when fundTxHash is null: how to record it by passing txHash.
onChainOmitidoNotrue if the on-chain read was skipped for budget reasons: do not poll in a loop.
anomaliaDetalleNoOnly with `anomalia`: what the discrepancy consists of.
autoLiberacionEnNoWhen the payment is released to the seller on expiry (ISO 8601), or null if there is no deposit yet.
cotizacionCaducaEnNoExpiry of the quote (ISO 8601), or null if it has none.
descargaDisponibleNoIs the download access already granted for this buyer?
sugerenciaSondeoSegundosNoHow many seconds to wait before polling again. 0 = there is nothing to wait for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed41 schema fields changed
    • changedInput schema / properties / ordenId / description
      Previous value: -"ALIAS RETIRADO de `orderId`: sigue funcionando, pero usa `orderId` (se quitará en una tanda futura, aún sin fecha). / DEPRECATED alias of `orderId`. El ordenId (uuid) de prepare_payment. Sin él, lista tus órdenes activas."New value: +"DEPRECATED alias of `orderId`: it still works, but use `orderId` (it will be removed in a future round, no date yet). The ordenId (uuid) from prepare_payment. Without it, it lists your active orders."
    • changedInput schema / properties / orderId / description
      Previous value: -"El ordenId (uuid) de prepare_payment. Sin él, lista tus órdenes activas."New value: +"The ordenId (uuid) from prepare_payment. Without it, it lists your active orders."
    • changedInput schema / properties / txHash / description
      Previous value: -"Opcional: hash de tu transacción fundPurchase para verificarla."New value: +"Optional: hash of your fundPurchase transaction, to verify it."
    • changedOutput schema / properties / anomalia / description
      Previous value: -"Solo si base y cadena no se pueden reconciliar; el equipo ya fue avisado."New value: +"Only if the database and the chain cannot be reconciled; the team has already been notified."
    • changedOutput schema / properties / anomaliaDetalle / description
      Previous value: -"Solo con `anomalia`: en qué consiste la discrepancia."New value: +"Only with `anomalia`: what the discrepancy consists of."
    • changedOutput schema / properties / autoLiberacionEn / description
      Previous value: -"Cuándo se libera el pago al vendedor por vencimiento (ISO 8601), o null si aún no hay depósito."New value: +"When the payment is released to the seller on expiry (ISO 8601), or null if there is no deposit yet."
    • changedOutput schema / properties / compraId / description
      Previous value: -"Solo en el detalle: el identificador on-chain (bytes32)."New value: +"Only in the detail: the on-chain identifier (bytes32)."
    • changedOutput schema / properties / cotizacionCaducaEn / description
      Previous value: -"Vencimiento de la cotización (ISO 8601), o null si no tiene."New value: +"Expiry of the quote (ISO 8601), or null if it has none."
    • changedOutput schema / properties / depositoVisto / description
      Previous value: -"¿La cadena ya muestra el depósito? Si es true, NO vuelvas a depositar."New value: +"Does the chain already show the deposit? If true, do NOT deposit again."
    • changedOutput schema / properties / descargaDisponible / description
      Previous value: -"¿El acceso de descarga ya está concedido para este comprador?"New value: +"Is the download access already granted for this buyer?"
    • changedOutput schema / properties / estadoBd / description
      Previous value: -"Estado según la base de datos de Bernuvia."New value: +"State according to Bernuvia's database."
    • changedOutput schema / properties / estadoOnChain / description
      Previous value: -"Estado según el contrato, o null si la lectura se omitió o falló. \"none\" = sin depósito."New value: +"State according to the contract, or null if the read was skipped or failed. \"none\" = no deposit."
    • changedOutput schema / properties / finalizado / description
      Previous value: -"¿El depósito está en bloques finalizados? null si no se pudo determinar."New value: +"Is the deposit in finalized blocks? null if it could not be determined."
    • changedOutput schema / properties / fundTxHash / description
      Previous value: -"Hash de la transacción de depósito, o null si no consta (puede ser null aunque esté fondeada)."New value: +"Hash of the deposit transaction, or null if it is not on record (it can be null even when the order is funded)."
    • changedOutput schema / properties / importe / description
      Previous value: -"Solo en el detalle: el importe de la orden en las dos unidades."New value: +"Only in the detail: the amount of the order in both units."
    • changedOutput schema / properties / importe / properties / unidades / description
      Previous value: -"Unidades mínimas de USDC, como cadena decimal."New value: +"Minimal units of USDC, as a decimal string."
    • changedOutput schema / properties / importe / properties / usdc / description
      Previous value: -"El mismo importe en USDC humano, como cadena decimal."New value: +"The same amount in human USDC, as a decimal string."
    • changedOutput schema / properties / nota / description
      Previous value: -"Solo en el inventario: aclaración en texto de qué contiene la lista."New value: +"Only in the inventory: a text clarification of what the list contains."
    • changedOutput schema / properties / notaFundTxHash / description
      Previous value: -"Solo cuando fundTxHash es null: cómo registrarlo pasando txHash."New value: +"Only when fundTxHash is null: how to record it by passing txHash."
    • changedOutput schema / properties / notaOnChain / description
      Previous value: -"Solo si se omitió la lectura: por qué y cuándo volver."New value: +"Only if the read was skipped: why, and when to come back."
    • changedOutput schema / properties / onChainOmitido / description
      Previous value: -"true si la lectura on-chain se saltó por presupuesto: no sondees en bucle."New value: +"true if the on-chain read was skipped for budget reasons: do not poll in a loop."
    • changedOutput schema / properties / ordenId / description
      Previous value: -"Solo en el detalle: el uuid de la orden consultada."New value: +"Only in the detail: the uuid of the order queried."
    • changedOutput schema / properties / ordenes / description
      Previous value: -"Solo en el inventario (llamada SIN ordenId): tus órdenes activas, de la más nueva a la más vieja (máx. 20)."New value: +"Only in the inventory (call WITHOUT ordenId): your active orders, from the newest to the oldest (max. 20)."
    • changedOutput schema / properties / ordenes / items / properties / compraId / description
      Previous value: -"El identificador on-chain (bytes32) de la compra."New value: +"The on-chain identifier (bytes32) of the purchase."
    • changedOutput schema / properties / ordenes / items / properties / cotizacionCaducaEn / description
      Previous value: -"Vencimiento de su cotización (ISO 8601), o null si no tiene."New value: +"Expiry of its quote (ISO 8601), or null if it has none."
    • changedOutput schema / properties / ordenes / items / properties / creadaEn / description
      Previous value: -"Cuándo se creó la orden (ISO 8601)."New value: +"When the order was created (ISO 8601)."
    • changedOutput schema / properties / ordenes / items / properties / estado / description
      Previous value: -"Estado en la base: created, quoted, funded, delivered o disputed."New value: +"State in the database: created, quoted, funded, delivered or disputed."
    • changedOutput schema / properties / ordenes / items / properties / importeUsdc / description
      Previous value: -"Importe en USDC humano, como cadena decimal."New value: +"Amount in human USDC, as a decimal string."
    • changedOutput schema / properties / ordenes / items / properties / ordenId / description
      Previous value: -"El uuid de la orden: el que se pasa a las demás herramientas."New value: +"The uuid of the order: the one you pass to the other tools."
    • changedOutput schema / properties / ordenes / items / properties / plantillaSlug / description
      Previous value: -"Slug de la plantilla comprada, o null si ya no existe."New value: +"Slug of the purchased template, or null if it no longer exists."
    • changedOutput schema / properties / plantillaSlug / description
      Previous value: -"Slug de la plantilla, o null si ya no existe."New value: +"Slug of the template, or null if it no longer exists."
    • changedOutput schema / properties / siguientePaso / description
      Previous value: -"Solo en el detalle: qué hacer ahora, en una frase."New value: +"Only in the detail: what to do now, in one sentence."
    • changedOutput schema / properties / sincronizado / description
      Previous value: -"true si esta llamada movió el estado de la base para alinearlo con la cadena."New value: +"true if this call moved the state in the database to align it with the chain."
    • changedOutput schema / properties / sugerenciaSondeoSegundos / description
      Previous value: -"Cada cuántos segundos volver a sondear. 0 = no hay nada que esperar."New value: +"How many seconds to wait before polling again. 0 = there is nothing to wait for."
    • changedOutput schema / properties / tx / description
      Previous value: -"Solo si mandaste txHash: el veredicto sobre esa transacción. null si no lo mandaste."New value: +"Only if you sent txHash: the verdict on that transaction. null if you did not send it."
    • changedOutput schema / properties / tx / properties / correspondeAOrden / description
      Previous value: -"¿La envió tu wallet contra el contrato de custodia? null si no se pudo comprobar."New value: +"Was it sent by your wallet against the escrow contract? null if it could not be checked."
    • changedOutput schema / properties / tx / properties / fondeaEstaOrden / description
      Previous value: -"¿Su evento Funded es el de ESTA orden? null si no se pudo comprobar."New value: +"Is its Funded event the one of THIS order? null if it could not be checked."
    • changedOutput schema / properties / tx / properties / hash / description
      Previous value: -"El txHash consultado."New value: +"The txHash that was checked."
    • changedOutput schema / properties / tx / properties / nota / description
      Previous value: -"Qué significa el resultado y qué hacer."New value: +"What the result means and what to do."
    • changedOutput schema / properties / tx / properties / resultado / description
      Previous value: -"success, reverted, pending, absent, unknown, \"no-corresponde\" (no es tuya contra el escrow) u \"omitida\" (diferida por presupuesto)."New value: +"success, reverted, pending, absent, unknown, \"no-corresponde\" (not yours against the escrow) or \"omitida\" (deferred for budget reasons)."
    • changedOutput schema / properties / wallet / description
      Previous value: -"La wallet compradora de la orden."New value: +"The buyer wallet of the order."
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and delivers: it discloses that status is checked both in the database and on chain, enumerates the possible statuses, explains default listing behavior, and clarifies ownership/download restrictions. It also reveals that downloads become available as soon as the deposit is confirmed, which an agent could not infer from the schema alone.

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?

Three sentences carry the core purpose, default behavior, and ownership caveats without padding. The first sentence is somewhat dense with statuses and sources, but every sentence earns its place and the most important scoping information is front-loaded.

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?

Even though an output schema exists and covers return structure, the description supplies sufficient operational context: how to trigger a list vs single lookup, what statuses to expect, and what the agent can and cannot do with these orders. It does not explicitly state whether the call is read-only or what happens on error, but those are minor gaps for a status tool.

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% and the schema already documents txHash, ordenId, and orderId including the deprecation. The tool description reinforces the 'without it, lists active orders' behavior but adds no new parameter-level meaning beyond what the schema provides.

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 identifies the resource (an order the agent paid) and the kind of information returned (status, next step), and it scopes the tool to 'your' orders, which helps separate it from related tools like my_purchases or dispute_status. It lacks an explicit verb such as 'returns' or 'lists', so the purpose is clear but not maximally crisp.

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

Usage Guidelines4/5

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

It states that without an orderId the tool lists the agent's active orders, and explicitly excludes owner-paid web orders, which is a clear when/when-not boundary. It does not name an alternative sibling tool to use for the excluded case, so it falls just short of the 'explicit alternatives' level.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Bernuvia toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources