Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

download

Issues a temporary download link (10 min) for a purchase already paid, with the file's SHA-256 checksum to verify it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
compraIdNoDEPRECATED alias of `purchaseId`: it still works, but use `purchaseId` (it will be removed in a future round, no date yet). The «compraId» that my_purchases returns for that purchase (NOT the ordenId from prepare_payment).
purchaseIdNoThe «compraId» that my_purchases returns for that purchase (NOT the ordenId from prepare_payment).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe download URL, already signed.
nameYesName of the file exactly as the seller uploaded it.
noteYesHow to use the link and what to check about the file.
sha256YesSHA-256 fingerprint (hex) of the file, or null if it has not been computed yet.
expiresAtYesWhen the link expires (ISO 8601); null if that URL does not expire.
sizeBytesYesSize of the file in bytes.
contentTypeYesMIME type of the file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • changedInput schema / properties / compraId / description
      Previous value: -"ALIAS RETIRADO de `purchaseId`: sigue funcionando, pero usa `purchaseId` (se quitará en una tanda futura, aún sin fecha). / DEPRECATED alias of `purchaseId`. El «compraId» que devuelve my_purchases para esa compra (NO el ordenId de prepare_payment)."New value: +"DEPRECATED alias of `purchaseId`: it still works, but use `purchaseId` (it will be removed in a future round, no date yet). The «compraId» that my_purchases returns for that purchase (NOT the ordenId from prepare_payment)."
    • changedInput schema / properties / purchaseId / description
      Previous value: -"El «compraId» que devuelve my_purchases para esa compra (NO el ordenId de prepare_payment)."New value: +"The «compraId» that my_purchases returns for that purchase (NOT the ordenId from prepare_payment)."
    • changedOutput schema / properties / contentType / description
      Previous value: -"Tipo MIME del archivo."New value: +"MIME type of the file."
    • changedOutput schema / properties / expiresAt / description
      Previous value: -"Cuándo caduca el enlace (ISO 8601); null si esa URL no caduca."New value: +"When the link expires (ISO 8601); null if that URL does not expire."
    • changedOutput schema / properties / name / description
      Previous value: -"Nombre del archivo tal y como lo subió el vendedor."New value: +"Name of the file exactly as the seller uploaded it."
    • changedOutput schema / properties / note / description
      Previous value: -"Cómo usar el enlace y qué comprobar del archivo."New value: +"How to use the link and what to check about the file."
    • changedOutput schema / properties / sha256 / description
      Previous value: -"Huella SHA-256 (hex) del archivo, o null si aún no se ha calculado."New value: +"SHA-256 fingerprint (hex) of the file, or null if it has not been computed yet."
    • changedOutput schema / properties / sizeBytes / description
      Previous value: -"Tamaño del archivo en bytes."New value: +"Size of the file in bytes."
    • changedOutput schema / properties / url / description
      Previous value: -"La URL de descarga, ya firmada."New value: +"The download URL, already signed."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden, and it does disclose important behavior: the link is temporary (10 minutes) and includes a SHA-256 checksum for verification. It does not mention failure modes or whether issuing a new link invalidates a previous one, but the disclosed traits are substantive.

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 a single front-loaded sentence with no filler. It packs the essential facts—temporary link, duration, prerequisite, and checksum—into a compact and immediately actionable form.

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?

The description plus a rich schema and an output schema cover the essential agent needs: what the tool does, the ID to supply, and the link's validity period. It does not spell out error behavior for unpaid purchases or authentication requirements, but for a two-parameter tool this is a minor gap.

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 schema itself already documents purchaseId and compraId, including the deprecated alias and the warning not to use ordenId. The tool description adds no parameter-level detail beyond the paid-purchase context, so the baseline score of 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 uses a specific verb ('Issues') and a specific resource ('temporary download link for a purchase already paid'), and adds the distinguishing detail of a SHA-256 checksum. It is immediately clear this is the download counterpart to upload-focused siblings like evidence_upload_link and zip_upload_link.

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 states the key precondition: the purchase must already be paid. The schema further clarifies which identifier to use by warning against the ordenId from prepare_payment. It does not explicitly name alternatives or say when not to use the tool, but the qualifying condition is clear enough for correct selection.

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