Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

close_expired_dispute

Only when YOUR dispute's deadline expired without resolution: resolveDisputeByTimeout(orderId) calldata against the escrow contract the order was funded in. The deadline that counts is plazoEfectivo, which dispute_status reads with the read scope (the team may have extended it); even if you cannot read it, the rejection says from when if it has not expired yet. It credits the FULL amount (no fee) to YOUR wallet inside the escrow, because it is the one that deposited: to move it to your wallet call the contract's withdraw() from it (you have no withdrawal_data, and you never withdraw your owner's money).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ordenIdNoDEPRECATED alias of `orderId`: it still works, but use `orderId` (it will be removed in a future round, no date yet). The ordenId (uuid) of the order whose dispute has expired.
orderIdNoThe ordenId (uuid) of the order whose dispute has expired.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
redYesThe network where it has to be sent.
walletYesThe buyer wallet: the only one that can send this transaction.
importeYesThe FULL amount that is credited to the buyer, with no fee.
ordenIdYesThe uuid of the order in Bernuvia.
compraIdYesThe on-chain identifier (bytes32) of the purchase.
contratoYesThe escrow contract OF THIS ORDER (not the current one): an old order lives in its own version.
prorrogadaYestrue if the committee extended the deadline (only in the contracts that support it).
advertenciaYesThat the amount is CREDITED inside the escrow and still has to be withdrawn.
transaccionYesThe envelope ready to sign and send from `wallet`.
instruccionesYesSteps in text, in order.
plazoVencidoElYesInstant when the dispute deadline expired (ISO 8601), or null if it could not be determined.
sondeoSegundosYesHow many seconds to wait between dispute_status polls after sending the transaction.
cierreAbiertoACualquieraDesdeYesFrom when anyone can close it, not just you (ISO 8601), or null if it does not apply.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed31 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 la orden en disputa vencida."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) of the order whose dispute has expired."
    • changedInput schema / properties / orderId / description
      Previous value: -"El ordenId (uuid) de la orden en disputa vencida."New value: +"The ordenId (uuid) of the order whose dispute has expired."
    • changedOutput schema / properties / advertencia / description
      Previous value: -"Que el importe se ACREDITA dentro del escrow y aún hay que retirarlo."New value: +"That the amount is CREDITED inside the escrow and still has to be withdrawn."
    • changedOutput schema / properties / cierreAbiertoACualquieraDesde / description
      Previous value: -"Desde cuándo puede cerrarla cualquiera, no solo tú (ISO 8601), o null si no aplica."New value: +"From when anyone can close it, not just you (ISO 8601), or null if it does not apply."
    • changedOutput schema / 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 / contrato / description
      Previous value: -"El contrato de custodia DE ESTA ORDEN (no el vigente): una orden antigua vive en su versión."New value: +"The escrow contract OF THIS ORDER (not the current one): an old order lives in its own version."
    • changedOutput schema / properties / contrato / properties / version / description
      Previous value: -"Versión del escrow (1, 2, 3 o 31 = v3.1)."New value: +"Escrow version (1, 2, 3 or 31 = v3.1)."
    • changedOutput schema / properties / importe / description
      Previous value: -"El importe ÍNTEGRO que se acredita al comprador, sin comisión."New value: +"The FULL amount that is credited to the buyer, with no fee."
    • 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 / instrucciones / description
      Previous value: -"Pasos en texto, en orden."New value: +"Steps in text, in order."
    • changedOutput schema / properties / ordenId / description
      Previous value: -"El uuid de la orden en Bernuvia."New value: +"The uuid of the order in Bernuvia."
    • changedOutput schema / properties / plazoVencidoEl / description
      Previous value: -"Instante en que venció el plazo de la disputa (ISO 8601), o null si no se pudo determinar."New value: +"Instant when the dispute deadline expired (ISO 8601), or null if it could not be determined."
    • changedOutput schema / properties / prorrogada / description
      Previous value: -"true si el comité prorrogó el plazo (solo en los contratos que lo admiten)."New value: +"true if the committee extended the deadline (only in the contracts that support it)."
    • changedOutput schema / properties / red / description
      Previous value: -"La red donde hay que enviarla."New value: +"The network where it has to be sent."
    • changedOutput schema / properties / red / properties / chainId / description
      Previous value: -"Id de la cadena (137 = Polygon)."New value: +"Chain id (137 = Polygon)."
    • changedOutput schema / properties / sondeoSegundos / description
      Previous value: -"Cada cuántos segundos sondear dispute_status tras enviar la transacción."New value: +"How many seconds to wait between dispute_status polls after sending the transaction."
    • changedOutput schema / properties / transaccion / description
      Previous value: -"El sobre listo para firmar y enviar desde `wallet`."New value: +"The envelope ready to sign and send from `wallet`."
    • changedOutput schema / properties / transaccion / properties / calculadoEn / description
      Previous value: -"Cuándo se estimaron las tarifas (ISO 8601). Ausente si no se pudieron estimar."New value: +"When the fees were estimated (ISO 8601). Absent if they could not be estimated."
    • changedOutput schema / properties / transaccion / properties / data / description
      Previous value: -"Calldata ya codificado (0x…)."New value: +"Already encoded calldata (0x…)."
    • changedOutput schema / properties / transaccion / properties / descripcion / description
      Previous value: -"Qué hace la transacción y qué exige el contrato."New value: +"What the transaction does and what the contract requires."
    • changedOutput schema / properties / transaccion / properties / gasLimitSugerido / description
      Previous value: -"Límite de gas sugerido en DECIMAL (cadena). Se conserva por compatibilidad."New value: +"Suggested gas limit in DECIMAL (string). Kept for compatibility."
    • changedOutput schema / properties / transaccion / properties / gasLimitSugeridoHex / description
      Previous value: -"El MISMO límite en HEXADECIMAL con 0x: es el que exige el JSON-RPC."New value: +"The SAME limit in HEXADECIMAL with 0x: it is the one the JSON-RPC requires."
    • changedOutput schema / properties / transaccion / properties / maxFeePerGasSugerido / description
      Previous value: -"maxFeePerGas en wei, en DECIMAL (cadena). Ausente si no se pudieron estimar las tarifas."New value: +"maxFeePerGas in wei, in DECIMAL (string). Absent if the fees could not be estimated."
    • changedOutput schema / properties / transaccion / properties / maxFeePerGasSugeridoHex / description
      Previous value: -"El MISMO maxFeePerGas en HEXADECIMAL con 0x: lo que exige el JSON-RPC."New value: +"The SAME maxFeePerGas in HEXADECIMAL with 0x: what the JSON-RPC requires."
    • changedOutput schema / properties / transaccion / properties / maxPriorityFeePerGasSugerido / description
      Previous value: -"maxPriorityFeePerGas en wei, en DECIMAL (cadena). Ausente si no se pudieron estimar."New value: +"maxPriorityFeePerGas in wei, in DECIMAL (string). Absent if they could not be estimated."
    • changedOutput schema / properties / transaccion / properties / maxPriorityFeePerGasSugeridoHex / description
      Previous value: -"El MISMO maxPriorityFeePerGas en HEXADECIMAL con 0x: lo que exige el JSON-RPC."New value: +"The SAME maxPriorityFeePerGas in HEXADECIMAL with 0x: what the JSON-RPC requires."
    • changedOutput schema / properties / transaccion / properties / nombre / description
      Previous value: -"Función del contrato: openDispute, cancelDispute o resolveDisputeByTimeout."New value: +"Contract function: openDispute, cancelDispute or resolveDisputeByTimeout."
    • changedOutput schema / properties / transaccion / properties / to / description
      Previous value: -"Dirección del contrato de custodia de esta orden."New value: +"Address of the escrow contract of this order."
    • changedOutput schema / properties / transaccion / properties / value / description
      Previous value: -"POL nativo a enviar, en HEXADECIMAL con 0x (QUANTITY del JSON-RPC): siempre \"0x0\"."New value: +"Native POL to send, in HEXADECIMAL with 0x (JSON-RPC QUANTITY): always \"0x0\"."
    • changedOutput schema / properties / wallet / description
      Previous value: -"La wallet compradora: la única que puede enviar esta transacción."New value: +"The buyer wallet: the only one that can send this transaction."
  2. First observed

TDQS

A4.4/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 behavioral burden and does so thoroughly: it explains deadline semantics, full-amount/no-fee crediting to the caller's escrow wallet, the need to call withdraw() afterward, and the prohibition on withdrawing the owner's money. It also notes what the rejection tells you when the deadline has not expired.

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?

The description is a single dense paragraph but is front-loaded with the eligibility condition and every sentence contributes operational detail. It is longer than strictly minimal, yet the length is justified by the complex contract interaction being described.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and a nontrivial escrow operation, the description covers when to use it, how to confirm the deadline, what outcome to expect, and the follow-up withdraw action. The output schema exists, so the absence of return-value explanation is not a gap.

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 the schema already documents orderId and the deprecated ordenId alias. The description only restates orderId in the calldata signature and adds no new parameter-level meaning, so the baseline score is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a precise action (resolveDisputeByTimeout(orderId) calldata), the target resource (the escrow contract), and the triggering condition (deadline expired without resolution). This is specific enough to distinguish the tool from siblings like open_dispute and withdraw_dispute.

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 gives an explicit 'Only when' condition and explains how to verify the deadline via dispute_status, including the possibility of extension. It does not name sibling alternatives, but the condition is clear and actionable.

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