Bernuvia

dispute_status

THE STATUS AND DEADLINES OF ONE of your orders and its dispute, asked for by order id: pick it when you already know which order you mean and you need the clock and the next step. Not for finding out WHICH cases or disputes you have, nor for the message thread (that is my_cases, the list), and not for the evidence file (that is my_evidence). It returns who opened it and when, what is left of the dispute window, the effective deadline (effectiveDeadline) and whether the team extended it, remaining reopenings, when it can be closed by timeout, whether there is a decision and whether it was executed, and what you can do. The seller only reads status and deadlines: no thread, no evidence, no actions.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`orderId`	Yes	Id of the order: the orderId (uuid) or the purchaseId returned by my_purchases and my_sales.

Output Schema

TableJSON Schema

Name	Required	Description
`can`	Yes	Which actions are possible now, with the reason when they are not.
`note`	Yes	Notice for the caller, in English.
`caseId`	Yes	Id of the support thread that is YOUR OWN; null if it is not yours or does not exist.
`status`	Yes	Current state of the order (the one on chain when it could be read).
`dispute`	Yes	The open dispute. With `open: false` it carries no other field.
`orderId`	Yes	Id (uuid) of the order.
`extended`	Yes	Did the committee extend the deadline by 30 days?
`yourRole`	Yes	Your role in the order: "buyer" or "seller".
`chainRead`	Yes	false = the chain could not be read and the answer comes from what is stored.
`stateInDb`	Yes	State stored in the database, which may lag behind the chain.
`caseClosed`	Yes	Is that thread closed? null when there is no thread of your own.
`purchaseId`	Yes	Hash of the order on chain (the `purchaseId` from my_purchases).
`reopensLeft`	Yes	Times the dispute can still be reopened.
`decisionMade`	Yes	Is there a written committee decision?
`disputeWindow`	Yes	Window in which a dispute can still be opened.
`contractVersion`	Yes	Version of the escrow contract THIS order lives in.
`openToAnyoneFrom`	Yes	From when anyone can send the closure (informational).
`effectiveDeadline`	Yes	CURRENT deadline (extension and pauses included), in ISO 8601.
`resolutionExecuted`	Yes	Has the split already been executed on chain?
`expiryCloseAvailableAt`	Yes	When it will be possible to close on expiry; null = it is already possible or there is nothing to close.

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedSep 27, 2026

removedInput schema / allOf

Removed value: -[
-  {
-    "anyOf": [
-      {
-        "required": [
-          "orderId"
-        ]
-      },
-      {
-        "required": [
-          "ordenId"
-        ]
-      }
-    ]
-  }
-]

removedInput schema / properties / ordenId

Removed value: -{
-  "deprecated": true,
-  "description": "DEPRECATED alias of `orderId`: it still works, but use `orderId` (it will be removed in a future round, no date yet). Id of the order: the ordenId (uuid) or the compraId returned by my_purchases and my_sales.",
-  "type": "string"
-}

changedInput schema / properties / orderId / description

Previous value: -"Id of the order: the ordenId (uuid) or the compraId returned by my_purchases and my_sales."New value: +"Id of the order: the orderId (uuid) or the purchaseId returned by my_purchases and my_sales."

addedInput schema / required
```
Added value: +[
+  "orderId"
+]
```

removedInput schema / x-bernuvia-aliases

Removed value: -{
-  "orderId": "ordenId"
-}

changedOutput schema / properties / can / properties / closeOnExpiry / properties / detail / description

Previous value: -"Only with can=false: the reason explained in the language of the call."New value: +"Only with can=false: the reason explained in English."

changedOutput schema / properties / can / properties / closeOnExpiry / properties / why / description

Previous value: -"Only with can=false: stable reason code (SOLO_COMPRADOR, VENTANA_CERRADA…)."New value: +"Only with can=false: stable reason code (BUYER_ONLY, WINDOW_CLOSED…)."

changedOutput schema / properties / can / properties / openDispute / properties / detail / description

Previous value: -"Only with can=false: the reason explained in the language of the call."New value: +"Only with can=false: the reason explained in English."

changedOutput schema / properties / can / properties / openDispute / properties / why / description

Previous value: -"Only with can=false: stable reason code (SOLO_COMPRADOR, VENTANA_CERRADA…)."New value: +"Only with can=false: stable reason code (BUYER_ONLY, WINDOW_CLOSED…)."

changedOutput schema / properties / can / properties / withdrawDispute / properties / detail / description

Previous value: -"Only with can=false: the reason explained in the language of the call."New value: +"Only with can=false: the reason explained in English."

changedOutput schema / properties / can / properties / withdrawDispute / properties / why / description

Previous value: -"Only with can=false: stable reason code (SOLO_COMPRADOR, VENTANA_CERRADA…)."New value: +"Only with can=false: stable reason code (BUYER_ONLY, WINDOW_CLOSED…)."

changedOutput schema / properties / dispute / properties / openedBy / description

Previous value: -"Who opened it: \"buyer\", \"seller\" or \"desconocido\"."New value: +"Who opened it: \"buyer\", \"seller\" or \"unknown\"."

changedOutput schema / properties / note / description

Previous value: -"Notice for the caller, in the language of the call."New value: +"Notice for the caller, in English."

changedOutput schema / properties / purchaseId / description

Previous value: -"Hash of the order on chain (the `compraId` from my_purchases)."New value: +"Hash of the order on chain (the `purchaseId` from my_purchases)."

Changed39 schema fields changedSep 23, 2026

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`. Id de la orden: el ordenId (uuid) o el compraId que devuelven my_purchases y my_sales."New value: +"DEPRECATED alias of `orderId`: it still works, but use `orderId` (it will be removed in a future round, no date yet). Id of the order: the ordenId (uuid) or the compraId returned by my_purchases and my_sales."

changedInput schema / properties / orderId / description

Previous value: -"Id de la orden: el ordenId (uuid) o el compraId que devuelven my_purchases y my_sales."New value: +"Id of the order: the ordenId (uuid) or the compraId returned by my_purchases and my_sales."

changedOutput schema / properties / can / description

Previous value: -"Qué acciones caben ahora, con el motivo cuando no caben."New value: +"Which actions are possible now, with the reason when they are not."

changedOutput schema / properties / can / properties / closeOnExpiry / properties / can / description
```
Previous value: -"¿Se puede hacer ahora mismo?"New value: +"Can this be done right now?"
```

changedOutput schema / properties / can / properties / closeOnExpiry / properties / detail / description

Previous value: -"Solo con can=false: el motivo explicado en el idioma de la llamada."New value: +"Only with can=false: the reason explained in the language of the call."

changedOutput schema / properties / can / properties / closeOnExpiry / properties / why / description

Previous value: -"Solo con can=false: código estable del motivo (SOLO_COMPRADOR, VENTANA_CERRADA…)."New value: +"Only with can=false: stable reason code (SOLO_COMPRADOR, VENTANA_CERRADA…)."

changedOutput schema / properties / can / properties / openDispute / properties / can / description
```
Previous value: -"¿Se puede hacer ahora mismo?"New value: +"Can this be done right now?"
```

changedOutput schema / properties / can / properties / openDispute / properties / detail / description

Previous value: -"Solo con can=false: el motivo explicado en el idioma de la llamada."New value: +"Only with can=false: the reason explained in the language of the call."

changedOutput schema / properties / can / properties / openDispute / properties / why / description

Previous value: -"Solo con can=false: código estable del motivo (SOLO_COMPRADOR, VENTANA_CERRADA…)."New value: +"Only with can=false: stable reason code (SOLO_COMPRADOR, VENTANA_CERRADA…)."

changedOutput schema / properties / can / properties / withdrawDispute / properties / can / description
```
Previous value: -"¿Se puede hacer ahora mismo?"New value: +"Can this be done right now?"
```

changedOutput schema / properties / can / properties / withdrawDispute / properties / detail / description

Previous value: -"Solo con can=false: el motivo explicado en el idioma de la llamada."New value: +"Only with can=false: the reason explained in the language of the call."

changedOutput schema / properties / can / properties / withdrawDispute / properties / why / description

Previous value: -"Solo con can=false: código estable del motivo (SOLO_COMPRADOR, VENTANA_CERRADA…)."New value: +"Only with can=false: stable reason code (SOLO_COMPRADOR, VENTANA_CERRADA…)."

changedOutput schema / properties / caseClosed / description

Previous value: -"¿Está cerrado ese hilo? null cuando no hay hilo propio."New value: +"Is that thread closed? null when there is no thread of your own."

changedOutput schema / properties / caseId / description

Previous value: -"Id del hilo de soporte PROPIO; null si no es tuyo o no existe."New value: +"Id of the support thread that is YOUR OWN; null if it is not yours or does not exist."

changedOutput schema / properties / chainRead / description

Previous value: -"false = no se pudo leer la cadena y se responde con lo guardado."New value: +"false = the chain could not be read and the answer comes from what is stored."

changedOutput schema / properties / contractVersion / description

Previous value: -"Versión del contrato de custodia en el que vive ESTA orden."New value: +"Version of the escrow contract THIS order lives in."

changedOutput schema / properties / decisionMade / description

Previous value: -"¿Hay una decisión del comité escrita?"New value: +"Is there a written committee decision?"

changedOutput schema / properties / dispute / description

Previous value: -"La disputa abierta. Con `open: false` no trae ningún otro campo."New value: +"The open dispute. With `open: false` it carries no other field."

changedOutput schema / properties / dispute / properties / deadlineAt / description

Previous value: -"Plazo de la disputa, en ISO 8601."New value: +"Deadline of the dispute, in ISO 8601."

changedOutput schema / properties / dispute / properties / hoursToDeadline / description

Previous value: -"Horas hasta ese plazo, con un decimal."New value: +"Hours until that deadline, with one decimal."

changedOutput schema / properties / dispute / properties / open / description

Previous value: -"¿Hay una disputa abierta?"New value: +"Is there an open dispute?"

changedOutput schema / properties / dispute / properties / openedAt / description

Previous value: -"Cuándo se abrió, en ISO 8601."New value: +"When it was opened, in ISO 8601."

changedOutput schema / properties / dispute / properties / openedBy / description

Previous value: -"Quién la abrió: \"buyer\", \"seller\" o \"desconocido\"."New value: +"Who opened it: \"buyer\", \"seller\" or \"desconocido\"."

changedOutput schema / properties / disputeWindow / description

Previous value: -"Ventana en la que todavía se puede abrir disputa."New value: +"Window in which a dispute can still be opened."

changedOutput schema / properties / disputeWindow / properties / closesAt / description

Previous value: -"Cuándo se cierra, en ISO 8601; null = no se sabe."New value: +"When it closes, in ISO 8601; null = unknown."

changedOutput schema / properties / disputeWindow / properties / hoursLeft / description

Previous value: -"Horas que quedan, con un decimal; null = no se sabe."New value: +"Hours left, with one decimal; null = unknown."

changedOutput schema / properties / disputeWindow / properties / open / description

Previous value: -"¿Sigue abierta ahora mismo?"New value: +"Is it still open right now?"

changedOutput schema / properties / effectiveDeadline / description

Previous value: -"Plazo VIGENTE (prórroga y pausas incluidas), en ISO 8601."New value: +"CURRENT deadline (extension and pauses included), in ISO 8601."

changedOutput schema / properties / expiryCloseAvailableAt / description

Previous value: -"Cuándo se podrá cerrar por vencimiento; null = ya se puede o no hay nada que cerrar."New value: +"When it will be possible to close on expiry; null = it is already possible or there is nothing to close."

changedOutput schema / properties / extended / description

Previous value: -"¿El comité prorrogó el plazo 30 días?"New value: +"Did the committee extend the deadline by 30 days?"

changedOutput schema / properties / note / description

Previous value: -"Aviso para quien llama, en el idioma de la llamada."New value: +"Notice for the caller, in the language of the call."

changedOutput schema / properties / openToAnyoneFrom / description

Previous value: -"Desde cuándo cualquiera puede enviar el cierre (informativo)."New value: +"From when anyone can send the closure (informational)."

changedOutput schema / properties / orderId / description

Previous value: -"Id (uuid) de la orden."New value: +"Id (uuid) of the order."

changedOutput schema / properties / purchaseId / description

Previous value: -"Hash de la orden en la cadena (el `compraId` de my_purchases)."New value: +"Hash of the order on chain (the `compraId` from my_purchases)."

changedOutput schema / properties / reopensLeft / description

Previous value: -"Veces que aún se puede reabrir la disputa."New value: +"Times the dispute can still be reopened."

changedOutput schema / properties / resolutionExecuted / description

Previous value: -"¿El reparto ya se ejecutó en la cadena?"New value: +"Has the split already been executed on chain?"

changedOutput schema / properties / stateInDb / description

Previous value: -"Estado guardado en la base, que puede ir por detrás de la cadena."New value: +"State stored in the database, which may lag behind the chain."

changedOutput schema / properties / status / description

Previous value: -"Estado vigente de la orden (el de la cadena cuando se pudo leer)."New value: +"Current state of the order (the one on chain when it could be read)."

changedOutput schema / properties / yourRole / description

Previous value: -"Tu papel en la orden: \"buyer\" o \"seller\"."New value: +"Your role in the order: \"buyer\" or \"seller\"."

First observedSep 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations, so the description carries the full burden; it discloses that this is read-only ("The seller only reads status and deadlines: no thread, no evidence, no actions") and enumerates the returned state (window, effectiveDeadline, extensions, reopenings, timeout, decision/execution). It omits permission/auth requirements and whether an extended deadline has side effects, so it stops short of a 5.

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?

Front-loads the core purpose and the exclusion list before the return-value inventory. It is somewhat run-on with all-caps emphasis and a long clause chain, but every sentence carries routing or behavioral information rather than filler.

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?

With an output schema present, the description need not explain return values, yet it still covers scope, exclusions, and the read-only constraint. For a single-param read tool this is thorough; minor gap is the absence of any permission/access note.

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 the single orderId's accepted formats (uuid or purchaseId from my_purchases/my_sales) are already documented in the schema. The description only restates "asked for by order id," adding no meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb (read status and deadlines) and resource (one order's dispute) scoped to a single order id, and explicitly names the siblings it is not (my_cases, my_evidence). An agent can distinguish it from order_status, my_cases and my_evidence without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit use condition ("pick it when you already know which order you mean and you need the clock and the next step") and excludes alternatives by name ("Not for finding out WHICH cases... that is my_cases", "not for the evidence file... my_evidence"). Routing is unambiguous.

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

All Bernuvia tools Inspect

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

Need Help?