Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

evidence_upload_link

Issues presigned URLs (1 h, the same expiry as every other MCP upload link) to PUT screenshots or PDFs that will serve as evidence in the dispute of an order you bought; it returns each one's storageRef, which is what submit_evidence asks for. With count it issues several at once, all of the same tipo (an evidence file usually carries several screenshots); the answer says how many it issued and when they expire. It asks for the ordenId and only issues them to that order's buyer. JPEG, PNG or PDF only, up to 10 MB each.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tipoNoDEPRECATED alias of `type`: it still works, but use `type` (it will be removed in a future round, no date yet). File type: image/jpeg, image/png or application/pdf. Nothing else.
typeNoFile type: image/jpeg, image/png or application/pdf. Nothing else.
countNoHow many links to issue at once, all of the same `tipo` (1-5; 1 by default). A case file usually carries several screenshots: asking for them in one call saves round trips. To mix types, one call per type.
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 whose case file you are going to add to (the ordenId or the compraId from my_purchases). Only the buyer of that order can file evidence.
orderIdNoId of the disputed order whose case file you are going to add to (the ordenId or the compraId from my_purchases). Only the buyer of that order can file evidence.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
linksYesOne link per file, all of the same `mimeType`. It may bring back fewer than requested if the upload quota runs out halfway.
issuedYesHow many links were actually issued.
maxBytesYesMaximum size in bytes of each file (this is not money: it is a count).
mimeTypeYesFile type these links accept.
expiresAtYesWhen the links expire, in ISO 8601.
expiresInYesHow long they last, said in words.
storageRefYesThe `storageRef` of the first link, repeated on its own.
instructionsYesWhat to do with the links, step by step.
presignedUrlYesThe first one in `links`, repeated on its own for older clients.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changed
    • changedInput schema / properties / count / description
      Previous value: -"Cuántos enlaces emitir de golpe, todos de ese mismo `tipo` (1-5; por defecto 1). Un expediente suele llevar varias capturas: pedirlas en una llamada ahorra viajes. Para mezclar tipos, una llamada por tipo. / How many links to issue at once, all of the same type."New value: +"How many links to issue at once, all of the same `tipo` (1-5; 1 by default). A case file usually carries several screenshots: asking for them in one call saves round trips. To mix types, one call per type."
    • 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 a cuyo expediente vas a aportar (el ordenId o el compraId de my_purchases). Solo el comprador de esa orden puede aportar pruebas."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 whose case file you are going to add to (the ordenId or the compraId from my_purchases). Only the buyer of that order can file evidence."
    • changedInput schema / properties / orderId / description
      Previous value: -"Id de la orden en disputa a cuyo expediente vas a aportar (el ordenId o el compraId de my_purchases). Solo el comprador de esa orden puede aportar pruebas."New value: +"Id of the disputed order whose case file you are going to add to (the ordenId or the compraId from my_purchases). Only the buyer of that order can file evidence."
    • changedInput schema / properties / tipo / description
      Previous value: -"ALIAS RETIRADO de `type`: sigue funcionando, pero usa `type` (se quitará en una tanda futura, aún sin fecha). / DEPRECATED alias of `type`. Tipo del archivo: image/jpeg, image/png o application/pdf. Nada más."New value: +"DEPRECATED alias of `type`: it still works, but use `type` (it will be removed in a future round, no date yet). File type: image/jpeg, image/png or application/pdf. Nothing else."
    • changedInput schema / properties / type / description
      Previous value: -"Tipo del archivo: image/jpeg, image/png o application/pdf. Nada más."New value: +"File type: image/jpeg, image/png or application/pdf. Nothing else."
    • changedOutput schema / properties / expiresAt / description
      Previous value: -"Cuándo caducan los enlaces, en ISO 8601."New value: +"When the links expire, in ISO 8601."
    • changedOutput schema / properties / expiresIn / description
      Previous value: -"Lo que duran, dicho en palabras."New value: +"How long they last, said in words."
    • changedOutput schema / properties / instructions / description
      Previous value: -"Qué hacer con los enlaces, paso a paso."New value: +"What to do with the links, step by step."
    • changedOutput schema / properties / issued / description
      Previous value: -"Cuántos enlaces se emitieron de verdad."New value: +"How many links were actually issued."
    • changedOutput schema / properties / links / description
      Previous value: -"Un enlace por archivo, todos del mismo `mimeType`. Puede traer menos de los pedidos si el cupo de subidas se agota a mitad."New value: +"One link per file, all of the same `mimeType`. It may bring back fewer than requested if the upload quota runs out halfway."
    • changedOutput schema / properties / links / items / properties / presignedUrl / description
      Previous value: -"URL firmada a la que se sube el archivo con un PUT."New value: +"Signed URL the file is uploaded to with a PUT."
    • changedOutput schema / properties / links / items / properties / storageRef / description
      Previous value: -"Referencia del archivo en el almacén; es lo que pide submit_evidence."New value: +"Reference of the file in the store; it is what submit_evidence asks for."
    • changedOutput schema / properties / maxBytes / description
      Previous value: -"Tamaño máximo en bytes de cada archivo (no es dinero: es una cuenta)."New value: +"Maximum size in bytes of each file (this is not money: it is a count)."
    • changedOutput schema / properties / mimeType / description
      Previous value: -"Tipo del archivo que aceptan estos enlaces."New value: +"File type these links accept."
    • changedOutput schema / properties / presignedUrl / description
      Previous value: -"El primero de `links`, repetido suelto para los clientes antiguos."New value: +"The first one in `links`, repeated on its own for older clients."
    • changedOutput schema / properties / storageRef / description
      Previous value: -"El `storageRef` del primer enlace, repetido suelto."New value: +"The `storageRef` of the first link, repeated on its own."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden, and it does so well: it states the 1-hour expiry, the storageRef return value, count semantics, buyer-only authorization, accepted formats, size cap, and that the answer reports how many links were issued and their expiry. It does not explicitly label the operation as non-mutating or describe error cases, but the observable behavior relevant to an agent is 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 dense but every sentence earns its place: purpose, output contract, count behavior, authorization, and constraints. It is front-loaded with the core action and resource, and the longer length is justified by the tool's conditional parameters and security context.

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?

All call-construction facts are present: required identifiers (orderId/ordenId and type/tipo), optional count, accepted media types, size limit, buyer-only authorization, and how the result feeds into submit_evidence. Since an output schema exists, the response shape does not need to be repeated in prose.

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 description coverage is 100%, and each parameter is already documented in detail, including deprecated aliases. The description adds cross-parameter meaning: `count` issues several links of the same `tipo`, `tipo` represents an evidence-file grouping, and the returned storageRef is exactly what submit_evidence expects. This lifts it above the schema-only baseline.

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 and resource: it issues presigned URLs for uploading evidence files (screenshots or PDFs) in the dispute of an order. It clearly ties the return value (storageRef) to submit_evidence, and the dispute-evidence context distinguishes it from generic upload sibling tools.

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 explains when to use the tool: before submitting evidence in an order dispute, by the buyer of the order, with explicit file-type and size limits. It also advises using `count` for multiple screenshots and one call per type when mixing types. It does not explicitly name image_upload_link or zip_upload_link as alternatives, so it stops short of full 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