Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

my_sales

Lists the builder's sales with their state and settlement. Each sale carries its orderId and whether the seller can still refund it (canRefund, and blockedReason when not).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of sales listed (1-200, default 50).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
salesYesThe paid sales, from the most recent to the oldest.
listedYesHow many sales go in `sales`.
totalsYesSeller totals over ALL its orders, not only the listed ones.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / limite
      Removed value: -{
-  "deprecated": true,
-  "description": "DEPRECATED alias of `limit`: it still works, but use `limit` (it will be removed in a future round, no date yet). Maximum number of sales listed (1-200, default 50).",
-  "type": "number"
-}
    • removedInput schema / x-bernuvia-aliases
      Removed value: -{
-  "limit": "limite"
-}
  2. Changed20 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Máximo de ventas listadas (1-200, por defecto 50)."New value: +"Maximum number of sales listed (1-200, default 50)."
    • changedInput schema / properties / limite / description
      Previous value: -"ALIAS RETIRADO de `limit`: sigue funcionando, pero usa `limit` (se quitará en una tanda futura, aún sin fecha). / DEPRECATED alias of `limit`. Máximo de ventas listadas (1-200, por defecto 50)."New value: +"DEPRECATED alias of `limit`: it still works, but use `limit` (it will be removed in a future round, no date yet). Maximum number of sales listed (1-200, default 50)."
    • changedOutput schema / properties / listed / description
      Previous value: -"Cuántas ventas van en `sales`."New value: +"How many sales go in `sales`."
    • changedOutput schema / properties / sales / description
      Previous value: -"Las ventas pagadas, de la más reciente a la más antigua."New value: +"The paid sales, from the most recent to the oldest."
    • changedOutput schema / properties / sales / items / properties / blockedReason / description
      Previous value: -"Código en inglés de por qué no se puede devolver; null cuando sí se puede."New value: +"Code (in English) for why it cannot be refunded; null when it can."
    • changedOutput schema / properties / sales / items / properties / buyer / description
      Previous value: -"@handle del comprador."New value: +"@handle of the buyer."
    • changedOutput schema / properties / sales / items / properties / canRefund / description
      Previous value: -"Se le puede ofrecer devolver al comprador."New value: +"A refund can be offered to the buyer."
    • changedOutput schema / properties / sales / items / properties / date / description
      Previous value: -"Fecha de la venta (ISO)."New value: +"Date of the sale (ISO)."
    • changedOutput schema / properties / sales / items / properties / grossUsdc / description
      Previous value: -"Bruto de la venta, en USDC."New value: +"Gross of the sale, in USDC."
    • changedOutput schema / properties / sales / items / properties / netUsdc / description
      Previous value: -"Neto real tras comisión y devoluciones, en USDC."New value: +"Real net after commission and refunds, in USDC."
    • changedOutput schema / properties / sales / items / properties / orderId / description
      Previous value: -"Uuid de la orden: es lo que pide `refund_sale`."New value: +"Uuid of the order: it is what `refund_sale` asks for."
    • changedOutput schema / properties / sales / items / properties / refundedUsdc / description
      Previous value: -"Devuelto al comprador, en USDC."New value: +"Refunded to the buyer, in USDC."
    • changedOutput schema / properties / sales / items / properties / slug / description
      Previous value: -"Slug de la plantilla (null si ya no existe)."New value: +"Slug of the template (null if it no longer exists)."
    • changedOutput schema / properties / sales / items / properties / status / description
      Previous value: -"Estado de la orden (funded, released, disputed…)."New value: +"State of the order (funded, released, disputed…)."
    • changedOutput schema / properties / sales / items / properties / template / description
      Previous value: -"Nombre de la plantilla vendida."New value: +"Name of the template sold."
    • changedOutput schema / properties / totals / description
      Previous value: -"Totales del vendedor sobre TODAS sus órdenes, no solo las listadas."New value: +"Seller totals over ALL its orders, not only the listed ones."
    • changedOutput schema / properties / totals / properties / grossUsdc / description
      Previous value: -"Bruto conservado, en USDC."New value: +"Gross kept, in USDC."
    • changedOutput schema / properties / totals / properties / inEscrowUsdc / description
      Previous value: -"Neto todavía en custodia, en USDC."New value: +"Net still in escrow, in USDC."
    • changedOutput schema / properties / totals / properties / releasedUsdc / description
      Previous value: -"Neto ya liberado, en USDC."New value: +"Net already released, in USDC."
    • changedOutput schema / properties / totals / properties / sales / description
      Previous value: -"Ventas liquidadas que no acabaron en devolución total."New value: +"Settled sales that did not end in a full refund."
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses what each sale record contains (orderId, canRefund, blockedReason), but says nothing about auth/permission requirements, pagination beyond the limit param, or whether this is a read-only operation, which an agent would want confirmed.

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?

Two tight sentences with zero filler, and the core purpose leads ahead of the per-record detail. Every clause earns its place.

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?

For a low-complexity, single-optional-param read tool with an output schema, this is nearly complete: the description covers purpose and the shape of the returned records, and the output schema handles field details. Only the lack of any usage routing or operation-safety note holds it back.

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 single limit parameter is fully documented in the schema (range 1-200, default 50). The description adds no parameter-level meaning, so the baseline 3 for schema-documented params applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Lists the builder's sales') plus the scope of what's returned (state and settlement). 'Builder's sales' implicitly separates it from buyer-side siblings like my_purchases, but no sibling is named explicitly, which is the only thing keeping this from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: an agent can infer this is the seller-side listing tool, but the description never says when to reach for it over closely related siblings such as my_purchases, order_status, or refund_sale. No exclusions or prerequisites are given.

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