Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

builder_stats

Returns the builder's sales stats by date range (count, gross, net, released, by day and by template) plus lifetime totals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoEnd date YYYY-MM-DD, inclusive (default: today).
fromNoStart date YYYY-MM-DD (default: 30 days ago).
desdeNoDEPRECATED alias of `from`: it still works, but use `from` (it will be removed in a future round, no date yet). Start date YYYY-MM-DD (default: 30 days ago).
hastaNoDEPRECATED alias of `to`: it still works, but use `to` (it will be removed in a future round, no date yet). End date YYYY-MM-DD, inclusive (default: today).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
byDayYesDaily series of the range.
rangeYesThe date range that was measured.
allTimeYesThe same totals over the seller's WHOLE history.
inRangeYesWhat was sold INSIDE the range.
byTemplateYesThe 10 best-selling templates of the range, from most to least.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed25 schema fields changed
    • changedInput schema / properties / desde / description
      Previous value: -"ALIAS RETIRADO de `from`: sigue funcionando, pero usa `from` (se quitará en una tanda futura, aún sin fecha). / DEPRECATED alias of `from`. Fecha inicial YYYY-MM-DD (por defecto hace 30 días)."New value: +"DEPRECATED alias of `from`: it still works, but use `from` (it will be removed in a future round, no date yet). Start date YYYY-MM-DD (default: 30 days ago)."
    • changedInput schema / properties / from / description
      Previous value: -"Fecha inicial YYYY-MM-DD (por defecto hace 30 días)."New value: +"Start date YYYY-MM-DD (default: 30 days ago)."
    • changedInput schema / properties / hasta / description
      Previous value: -"ALIAS RETIRADO de `to`: sigue funcionando, pero usa `to` (se quitará en una tanda futura, aún sin fecha). / DEPRECATED alias of `to`. Fecha final YYYY-MM-DD inclusive (por defecto hoy)."New value: +"DEPRECATED alias of `to`: it still works, but use `to` (it will be removed in a future round, no date yet). End date YYYY-MM-DD, inclusive (default: today)."
    • changedInput schema / properties / to / description
      Previous value: -"Fecha final YYYY-MM-DD inclusive (por defecto hoy)."New value: +"End date YYYY-MM-DD, inclusive (default: today)."
    • changedOutput schema / properties / allTime / description
      Previous value: -"Los mismos totales sobre TODA la historia del vendedor."New value: +"The same totals over the seller's WHOLE history."
    • changedOutput schema / properties / allTime / properties / grossUsdc / description
      Previous value: -"Bruto conservado, en USDC."New value: +"Gross kept, in USDC."
    • changedOutput schema / properties / allTime / properties / inEscrowUsdc / description
      Previous value: -"Neto todavía en custodia, en USDC."New value: +"Net still in escrow, in USDC."
    • changedOutput schema / properties / allTime / properties / releasedUsdc / description
      Previous value: -"Neto ya liberado, en USDC."New value: +"Net already released, in USDC."
    • changedOutput schema / properties / allTime / properties / sales / description
      Previous value: -"Ventas liquidadas de siempre."New value: +"Settled sales of all time."
    • changedOutput schema / properties / byDay / description
      Previous value: -"Serie diaria del rango."New value: +"Daily series of the range."
    • changedOutput schema / properties / byDay / items / properties / day / description
      Previous value: -"Día YYYY-MM-DD."New value: +"Day YYYY-MM-DD."
    • changedOutput schema / properties / byDay / items / properties / netUsdc / description
      Previous value: -"Neto de ese día, en USDC."New value: +"Net of that day, in USDC."
    • changedOutput schema / properties / byDay / items / properties / sales / description
      Previous value: -"Ventas de ese día."New value: +"Sales of that day."
    • changedOutput schema / properties / byTemplate / description
      Previous value: -"Las 10 plantillas más vendidas del rango, de más a menos."New value: +"The 10 best-selling templates of the range, from most to least."
    • changedOutput schema / properties / byTemplate / items / properties / netUsdc / description
      Previous value: -"Neto de esa plantilla, en USDC."New value: +"Net of that template, in USDC."
    • changedOutput schema / properties / byTemplate / items / properties / sales / description
      Previous value: -"Ventas de esa plantilla en el rango."New value: +"Sales of that template in the range."
    • changedOutput schema / properties / byTemplate / items / properties / template / description
      Previous value: -"Nombre de la plantilla (null si ya no existe)."New value: +"Name of the template (null if it no longer exists)."
    • changedOutput schema / properties / inRange / description
      Previous value: -"Lo vendido DENTRO del rango."New value: +"What was sold INSIDE the range."
    • changedOutput schema / properties / inRange / properties / grossUsdc / description
      Previous value: -"Bruto conservado, en USDC."New value: +"Gross kept, in USDC."
    • changedOutput schema / properties / inRange / properties / netUsdc / description
      Previous value: -"Neto tras comisión, en USDC."New value: +"Net after commission, in USDC."
    • changedOutput schema / properties / inRange / properties / releasedUsdc / description
      Previous value: -"Neto ya liquidado, en USDC."New value: +"Net already settled, in USDC."
    • changedOutput schema / properties / inRange / properties / sales / description
      Previous value: -"Ventas pagadas que no acabaron en devolución total."New value: +"Paid sales that did not end in a full refund."
    • changedOutput schema / properties / range / description
      Previous value: -"El rango de fechas que se ha medido."New value: +"The date range that was measured."
    • changedOutput schema / properties / range / properties / from / description
      Previous value: -"Fecha inicial YYYY-MM-DD."New value: +"Start date YYYY-MM-DD."
    • changedOutput schema / properties / range / properties / to / description
      Previous value: -"Fecha final YYYY-MM-DD, inclusive."New value: +"End date YYYY-MM-DD, inclusive."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It does convey a read-only operation ('Returns') and the scope of results, which is useful, but it does not disclose details such as whether stats are for the current authenticated builder, how lifetime totals are computed, or any access requirements.

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 that begins with the action and resource, then packs the key metrics into a parenthetical list. There is no filler, repetition, or wasted wording.

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?

An output schema is present, so the description does not need to explain return values in detail. Combined with full parameter documentation and default dates in the schema, the description covers the core behavior well; it is only missing a small amount of usage context relative to sibling tools.

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%, so the schema already documents every parameter and the deprecated aliases. The description adds no parameter-level detail beyond what is in the schema, which is acceptable at the baseline of 3.

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 ('Returns') and identifies a concrete resource: the builder's sales stats. It also enumerates the exact aggregation dimensions (count, gross, net, released, by day, by template) and lifetime totals, which clearly distinguishes it from a plain sales-list tool like my_sales.

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

Usage Guidelines2/5

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

The description states what the tool returns but gives no guidance on when to choose it over siblings such as my_sales, deposit_data, or my_balance. There are no explicit alternatives, exclusions, or contextual triggers, so an agent must infer usage from the tool name and shape alone.

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