Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

withdraw_dispute

Withdraws a dispute YOU opened on an order you paid: cancelDispute(orderId) calldata for your wallet. The order goes back to escrow with whatever time it had left; if the window has already closed, withdrawing it leaves the order on its way to the seller and it cannot be reopened. Your owner cannot sign this for you.

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 disputed order.
orderIdNoThe ordenId (uuid) of the disputed order.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
redYesThe network where it has to be sent.
walletYesThe buyer wallet: the only one that can send this transaction.
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.
advertenciaYesConsequences of withdrawing it, depending on whether the window is still open.
transaccionYesThe envelope ready to sign and send from `wallet`.
instruccionesYesSteps in text, in order.
sondeoSegundosYesHow many seconds to wait between dispute_status polls after sending the transaction.
ventanaCierraEnYesWhen the dispute window closes (ISO 8601), or null if it could not be determined.
ventanaSigueAbiertaYestrue = you will be able to open the dispute again; false = withdrawing it is irreversible in practice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed27 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."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 disputed order."
    • changedInput schema / properties / orderId / description
      Previous value: -"El ordenId (uuid) de la orden en disputa."New value: +"The ordenId (uuid) of the disputed order."
    • changedOutput schema / properties / advertencia / description
      Previous value: -"Consecuencias de retirarla, según si la ventana sigue abierta."New value: +"Consequences of withdrawing it, depending on whether the window is still open."
    • 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 / 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 / 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 / ventanaCierraEn / description
      Previous value: -"Cuándo se cierra la ventana de disputa (ISO 8601), o null si no se pudo determinar."New value: +"When the dispute window closes (ISO 8601), or null if it could not be determined."
    • changedOutput schema / properties / ventanaSigueAbierta / description
      Previous value: -"true = podrás volver a abrir la disputa; false = retirarla es irreversible en la práctica."New value: +"true = you will be able to open the dispute again; false = withdrawing it is irreversible in practice."
    • 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.5/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 disclosure burden and does so well. It reveals that the tool produces cancelDispute calldata, explains the escrow/time-left effect, covers the expired-window edge case where the order proceeds to the seller and cannot be reopened, and states that the owner cannot sign this action.

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?

The description is two dense sentences that cover purpose, calldata form, state transition, an edge case, and a signing restriction with no wasted words. The key scoping statement appears first, making it easy to parse.

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 the output schema, the description does not need to explain return values. It covers preconditions, the escrow effect, the closed-window consequence, and the owner signing restriction, so the agent has enough context to decide when and how to call the tool correctly.

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%, and both orderId and the deprecated ordenId alias are already documented in the schema. The tool description adds little beyond naming orderId in the calldata string, so the high schema coverage yields a baseline score of 3.

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 states a specific verb and resource: 'Withdraws a dispute YOU opened on an order you paid' and identifies the concrete calldata form, 'cancelDispute(orderId) calldata for your wallet'. This clearly scopes the tool to the user's own disputes on paid orders rings and distinguishes it from sibling tools like open_dispute or close_expired_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 clear preconditions: only disputes the user opened and only orders the user paid. It also warns about the closed-window consequence, which implies when withdrawing may be harmful, but it does not explicitly name alternatives such as dispute_status or open_dispute.

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