Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

my_evidence

THE EVIDENCE YOU filed on the dispute of an order you bought, each with its date: pick it to check what the file already contains. Not for that dispute's status, deadlines or outcome (that is dispute_status), and not for the case message thread (that is my_cases). Never anyone else's, and buyer only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderIdYesId of the disputed order.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderYesId (uuid) of the order queried.
totalYesHow many pieces of your own evidence are in the case file.
statusYesState of the order exactly as the database stores it.
evidenceYesOnly what the caller filed: never another person's material.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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 disputed order.",
-  "type": "string"
-}
    • addedInput schema / required
      Added value: +[
+  "orderId"
+]
    • removedInput schema / x-bernuvia-aliases
      Removed value: -{
-  "orderId": "ordenId"
-}
  2. Changed9 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 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). Id of the disputed order."
    • changedInput schema / properties / orderId / description
      Previous value: -"Id de la orden en disputa."New value: +"Id of the disputed order."
    • changedOutput schema / properties / evidence / description
      Previous value: -"Solo lo que aportó quien llama: nunca material de otra persona."New value: +"Only what the caller filed: never another person's material."
    • changedOutput schema / properties / evidence / items / properties / date / description
      Previous value: -"Cuándo se aportó, en ISO 8601."New value: +"When it was filed, in ISO 8601."
    • changedOutput schema / properties / evidence / items / properties / file / description
      Previous value: -"Nombre del archivo adjunto, o null si la prueba era solo texto."New value: +"Name of the attached file, or null if the evidence was text only."
    • changedOutput schema / properties / evidence / items / properties / text / description
      Previous value: -"Lo que se escribió al aportarla."New value: +"What was written when filing it."
    • changedOutput schema / properties / order / description
      Previous value: -"Id (uuid) de la orden consultada."New value: +"Id (uuid) of the order queried."
    • changedOutput schema / properties / status / description
      Previous value: -"Estado de la orden tal y como lo guarda la base."New value: +"State of the order exactly as the database stores it."
    • changedOutput schema / properties / total / description
      Previous value: -"Cuántas pruebas propias hay en el expediente."New value: +"How many pieces of your own evidence are in the case file."
  3. 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 does disclose meaningful behavioral constraints: ownership scoping ('Never anyone else's, and buyer only') and that each item includes its date. It does not cover ordering, pagination or size limits, but the output schema exists so return shape is covered elsewhere.

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 resource and what it returns, then routes to alternatives in one dense sentence. Slightly awkward phrasing ('pick it to check what the file already contains') but no filler sentences.

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?

For a single-parameter read tool with a 100%-covered schema and an output schema, the description supplies everything missing: the scope of returned data, the ownership restriction, and the sibling routing. Nothing an agent needs to call it correctly is absent.

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 there is a single required parameter, so the schema already defines orderId. The description only loosely implies the id is for an order the caller bought, adding no syntax or format detail beyond the schema; 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+resource ('THE EVIDENCE YOU filed on the dispute of an order') and explicitly distinguishes itself from siblings by naming dispute_status and my_cases as the wrong tools for adjacent needs. An agent can select it 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 explicit when-to-use ('pick it to check what the file already contains') and two when-not conditions with the correct alternatives named ('Not for that dispute's status... that is dispute_status, and not for the case message thread... that is my_cases').

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