Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

submit_evidence

Files evidence on the dispute of an order you BOUGHT: the dispute belongs to the buyer and only the buyer files evidence (a seller is refused). The text explaining what it proves is mandatory; the file is optional. It goes to the team that resolves the case, not to the case thread. It opens no dispute and moves no money.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileNoOPTIONAL: the file already uploaded with evidence_upload_link. sha256 in lowercase hexadecimal of the exact content you uploaded.
textNoWhat this evidence proves, in 10-2000 characters. It is what whoever resolves the case reads, so it always goes even if you attach a file.
textoNoDEPRECATED alias of `text`: it still works, but use `text` (it will be removed in a future round, no date yet). What this evidence proves, in 10-2000 characters. It is what whoever resolves the case reads, so it always goes even if you attach a file.
archivoNoDEPRECATED alias of `file`: it still works, but use `file` (it will be removed in a future round, no date yet). OPTIONAL: the file already uploaded with evidence_upload_link. sha256 in lowercase hexadecimal of the exact content you uploaded.
ordenIdNoDEPRECATED 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 (the one returned by my_purchases, my_sales or order_status).
orderIdNoId of the disputed order (the one returned by my_purchases, my_sales or order_status).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesAlways true: a rejection arrives as an error, not as ok=false.
asPartyYesUnder which role it was recorded: "buyer" or "team".
nextStepYesWhat to do now: there is no automatic answer, a person decides.
recordedYesThe evidence was written into the case file.
withFileYesDid it carry an attached file besides the text?
pollSecondsYesHow many seconds, at most, it is worth waiting between polls of the status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • changedInput schema / properties / archivo / description
      Previous value: -"ALIAS RETIRADO de `file`: sigue funcionando, pero usa `file` (se quitará en una tanda futura, aún sin fecha). / DEPRECATED alias of `file`. OPCIONAL: el archivo ya subido con evidence_upload_link. sha256 en hexadecimal minúsculas del contenido exacto que subiste."New value: +"DEPRECATED alias of `file`: it still works, but use `file` (it will be removed in a future round, no date yet). OPTIONAL: the file already uploaded with evidence_upload_link. sha256 in lowercase hexadecimal of the exact content you uploaded."
    • changedInput schema / properties / file / description
      Previous value: -"OPCIONAL: el archivo ya subido con evidence_upload_link. sha256 en hexadecimal minúsculas del contenido exacto que subiste."New value: +"OPTIONAL: the file already uploaded with evidence_upload_link. sha256 in lowercase hexadecimal of the exact content you uploaded."
    • 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 (el que devuelven my_purchases, my_sales o order_status)."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 (the one returned by my_purchases, my_sales or order_status)."
    • changedInput schema / properties / orderId / description
      Previous value: -"Id de la orden en disputa (el que devuelven my_purchases, my_sales o order_status)."New value: +"Id of the disputed order (the one returned by my_purchases, my_sales or order_status)."
    • changedInput schema / properties / text / description
      Previous value: -"Qué demuestra esta prueba, en 10-2000 caracteres. Es lo que lee quien resuelve, así que va siempre aunque adjuntes archivo."New value: +"What this evidence proves, in 10-2000 characters. It is what whoever resolves the case reads, so it always goes even if you attach a file."
    • changedInput schema / properties / texto / description
      Previous value: -"ALIAS RETIRADO de `text`: sigue funcionando, pero usa `text` (se quitará en una tanda futura, aún sin fecha). / DEPRECATED alias of `text`. Qué demuestra esta prueba, en 10-2000 caracteres. Es lo que lee quien resuelve, así que va siempre aunque adjuntes archivo."New value: +"DEPRECATED alias of `text`: it still works, but use `text` (it will be removed in a future round, no date yet). What this evidence proves, in 10-2000 characters. It is what whoever resolves the case reads, so it always goes even if you attach a file."
    • changedOutput schema / properties / asParty / description
      Previous value: -"Con qué papel se anotó: \"buyer\" o \"team\"."New value: +"Under which role it was recorded: \"buyer\" or \"team\"."
    • changedOutput schema / properties / nextStep / description
      Previous value: -"Qué hacer ahora: no hay respuesta automática, decide una persona."New value: +"What to do now: there is no automatic answer, a person decides."
    • changedOutput schema / properties / ok / description
      Previous value: -"Siempre true: un rechazo llega como error, no como ok=false."New value: +"Always true: a rejection arrives as an error, not as ok=false."
    • changedOutput schema / properties / pollSeconds / description
      Previous value: -"Cada cuántos segundos como mucho conviene sondear el estado."New value: +"How many seconds, at most, it is worth waiting between polls of the status."
    • changedOutput schema / properties / recorded / description
      Previous value: -"La prueba quedó escrita en el expediente."New value: +"The evidence was written into the case file."
    • changedOutput schema / properties / withFile / description
      Previous value: -"¿Llevaba archivo adjunto además del texto?"New value: +"Did it carry an attached file besides the text?"
  2. First observed

TDQS

A4.7/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. It discloses the mandatory text ('text... is mandatory'), the optional file, the recipient (team vs thread), and explicitly states side effects ('opens no dispute and moves no money'). It does not mention error conditions or auth details, but the core behavioral traits are well covered.

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 three sentences, front-loading the most critical constraint (buyer-only) and then efficiently covering routing, mandatory text, and side effects. Every sentence carries unique information with no fluff.

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 action's complexity (6 parameters, aliases, nested objects) and the presence of an output schema, the description fully covers purpose, access control, side effects, and parameter requirements. It correctly points to evidence_upload_link for the file upload, which is available as a sibling tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value beyond the schema by explaining why the text is mandatory ('It is what whoever resolves the case reads, so it always goes even if you attach a file') and reinforcing the optional nature of the file. This gives contextual meaning to the parameter relationships.

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 ('files evidence'), a precise resource ('dispute of an order you BOUGHT'), and a clear ownership constraint ('only the buyer files evidence'). It distinguishes itself from siblings like open_dispute, reply_to_case, and withdraw_dispute by specifying what it does not do ('opens no dispute and moves no money').

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?

Explicitly states who may use it ('buyer only') and who is refused ('a seller is refused'), and clarifies routing ('goes to the team that resolves the case, not to the case thread') to differentiate from reply_to_case. It also tells what it does not do, giving clear when-to-use and when-not-to-use guidance.

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