Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

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 (plazoEfectivo) 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
NameRequiredDescriptionDefault
ordenIdNoDEPRECATED 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.
orderIdNoId of the order: the ordenId (uuid) or the compraId returned by my_purchases and my_sales.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
canYesWhich actions are possible now, with the reason when they are not.
noteYesNotice for the caller, in the language of the call.
caseIdYesId of the support thread that is YOUR OWN; null if it is not yours or does not exist.
statusYesCurrent state of the order (the one on chain when it could be read).
disputeYesThe open dispute. With `open: false` it carries no other field.
orderIdYesId (uuid) of the order.
extendedYesDid the committee extend the deadline by 30 days?
yourRoleYesYour role in the order: "buyer" or "seller".
chainReadYesfalse = the chain could not be read and the answer comes from what is stored.
stateInDbYesState stored in the database, which may lag behind the chain.
caseClosedYesIs that thread closed? null when there is no thread of your own.
purchaseIdYesHash of the order on chain (the `compraId` from my_purchases).
reopensLeftYesTimes the dispute can still be reopened.
decisionMadeYesIs there a written committee decision?
disputeWindowYesWindow in which a dispute can still be opened.
contractVersionYesVersion of the escrow contract THIS order lives in.
openToAnyoneFromYesFrom when anyone can send the closure (informational).
effectiveDeadlineYesCURRENT deadline (extension and pauses included), in ISO 8601.
resolutionExecutedYesHas the split already been executed on chain?
expiryCloseAvailableAtYesWhen 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.

  1. Changed39 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`. 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\"."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and states that this is a read-only operation: 'The seller only reads status and deadlines: no thread, no evidence, no actions.' It also discloses what the response reports (deadlines, reopenings, decision, execution), even though an output schema exists.

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 longer than average, but almost every sentence earns its place: selection criteria, exclusions, and behavior. The enumeration of returned fields is slightly redundant with the output schema, but it is still organized and front-loaded with the core purpose.

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?

The description covers the required parameter, selection context, exclusion of siblings, and the read-only nature of the call. Combined with a full input schema and an output schema, an agent has everything needed to choose and invoke this 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?

The schema already provides 100% parameter coverage with detailed descriptions of orderId and the deprecated ordenId alias. The description only says 'asked for by order id,' which adds no meaningful information beyond the schema, so the 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 names a clear verb+resource combination: retrieving the status and deadlines of one order's dispute by order id. It explicitly distinguishes itself from siblings (my_cases, my_evidence) rather than merely restating the tool name.

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?

It gives an explicit selection condition: use when you already know which order you mean and need the clock and next step. It also tells when not to use it, naming the alternatives for case lists and evidence files, leaving no ambiguity.

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