Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

open_dispute

DISPUTE of an order YOU paid: on chain the buyer is your wallet, so only you can open it. It creates the case with your written reason and returns the openDispute(orderId) calldata that YOU sign with your linked wallet; until it is mined there is no dispute. Your owner sees the case and files evidence from the web, but does not sign this. Afterwards, if your token carries the read scope, poll dispute_status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
motivoNoDEPRECATED alias of `reason`: it still works, but use `reason` (it will be removed in a future round, no date yet). What went wrong and what you expected to receive, in 10-2000 characters. It is the first piece of evidence of the case and the person who resolves it reads it.
reasonNoWhat went wrong and what you expected to receive, in 10-2000 characters. It is the first piece of evidence of the case and the person who resolves it reads 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) of the order held in escrow.
orderIdNoThe ordenId (uuid) of the order held in escrow.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
redYesThe network where it has to be sent.
casoIdYesId of the case thread, already created with your motivo even if the transaction never gets mined.
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.
advertenciaYesWhat you have to know before signing: there is no dispute until the transaction is mined.
transaccionYesThe envelope ready to sign and send from `wallet`.
casoYaExistiaYestrue if the thread was already open and no new one was created.
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): after that the contract reverts DisputeWindowClosed. null if it could not be determined.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed30 schema fields changed
    • changedInput schema / properties / motivo / description
      Previous value: -"ALIAS RETIRADO de `reason`: sigue funcionando, pero usa `reason` (se quitará en una tanda futura, aún sin fecha). / DEPRECATED alias of `reason`. Qué falló y qué esperabas recibir, en 10-2000 caracteres. Es la primera prueba del caso y la lee la persona que resuelve."New value: +"DEPRECATED alias of `reason`: it still works, but use `reason` (it will be removed in a future round, no date yet). What went wrong and what you expected to receive, in 10-2000 characters. It is the first piece of evidence of the case and the person who resolves it reads it."
    • 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 custodia."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 held in escrow."
    • changedInput schema / properties / orderId / description
      Previous value: -"El ordenId (uuid) de la orden en custodia."New value: +"The ordenId (uuid) of the order held in escrow."
    • changedInput schema / properties / reason / description
      Previous value: -"Qué falló y qué esperabas recibir, en 10-2000 caracteres. Es la primera prueba del caso y la lee la persona que resuelve."New value: +"What went wrong and what you expected to receive, in 10-2000 characters. It is the first piece of evidence of the case and the person who resolves it reads it."
    • changedOutput schema / properties / advertencia / description
      Previous value: -"Lo que hay que saber antes de firmar: no hay disputa hasta que la transacción se mine."New value: +"What you have to know before signing: there is no dispute until the transaction is mined."
    • changedOutput schema / properties / casoId / description
      Previous value: -"Id del hilo del caso, ya creado con tu motivo aunque la transacción no llegue a minarse."New value: +"Id of the case thread, already created with your motivo even if the transaction never gets mined."
    • changedOutput schema / properties / casoYaExistia / description
      Previous value: -"true si el hilo ya estaba abierto y no se creó uno nuevo."New value: +"true if the thread was already open and no new one was created."
    • 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): después el contrato revierte DisputeWindowClosed. null si no se pudo determinar."New value: +"When the dispute window closes (ISO 8601): after that the contract reverts DisputeWindowClosed. null if it could not be determined."
    • 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?

No annotations exist, so the description carries the full burden. It discloses the on-chain nature, that the dispute only exists after the transaction is mined, that the calldata must be signed by the user's wallet, and that the owner handles evidence separately. This goes well beyond a simple side-effect note.

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 that front-loads the core purpose and role limitation. Each sentence adds critical process information without excess. Slightly longer than strictly necessary but well structured.

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 tool's complexity (on-chain signing, role separation, pending state), the description is remarkably complete: it covers preconditions, action, outcome, timing, and follow-up steps. The presence of an output schema and 100% parameter coverage covers the remaining detail.

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 input schema already describes all four parameters (orderId, reason, and deprecated aliases) with 100% coverage, so the description adds little beyond referencing the orderId in the calldata and the reason generally. Baseline 3 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 clearly states the tool opens a dispute on an order the caller paid, creates a case with a written reason, and returns calldata for signing. This distinguishes it from dispute_status, close_expired_dispute, and withdraw_dispute, and explicitly states the buyer role limitation.

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?

The description gives clear context: only the buyer (the wallet that paid) can open the dispute, and the owner/agent does not sign this calldata – evidence filing is a separate step. It also advises polling dispute_status afterwards if the read scope is present. While it doesn't name sibling tools for closing/withdrawing, the conditions for use are explicit.

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