Bernuvia

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

Name	Required	Description	Default
`to`	No	End date YYYY-MM-DD, inclusive (default: today).
`from`	No	Start date YYYY-MM-DD (default: 30 days ago).

Output Schema

TableJSON Schema

Name	Required	Description
`byDay`	Yes	Daily series of the range.
`range`	Yes	The date range that was measured.
`allTime`	Yes	The same totals over the seller's WHOLE history.
`inRange`	Yes	What was sold INSIDE the range.
`byTemplate`	Yes	The 10 best-selling templates of the range, from most to least.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 27, 2026

removedInput schema / properties / desde

Removed value: -{
-  "deprecated": true,
-  "description": "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).",
-  "type": "string"
-}

removedInput schema / properties / hasta

Removed value: -{
-  "deprecated": true,
-  "description": "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).",
-  "type": "string"
-}

removedInput schema / x-bernuvia-aliases

Removed value: -{
-  "from": "desde",
-  "to": "hasta"
-}

Changed25 schema fields changedSep 23, 2026

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."

First observedSep 23, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations are provided, so the description must carry behavioral disclosure. 'Returns' implies a safe read, and it discloses the aggregate shape of the response, but it says nothing about pagination, permissions, or how date-range boundaries behave. Since an output schema exists, the return-shape detail is partly redundant.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that packs the resource and all returned dimensions with no filler. It is dense but readable; no sentence is wasted.

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 read-only, no-required-parameter stats tool with a fully documented schema and an output schema, the description covers what the tool does and what it returns. The only real gap is the lack of routing guidance versus sibling sales/balance 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% and both parameters ('from'/'to') already document format and defaults. The description only restates 'by date range' without adding syntax, inclusivity, or default behavior beyond the schema, so the baseline 3 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+resource ('Returns the builder's sales stats') and enumerates the metric dimensions (count, gross, net, released, by day, by template) plus lifetime totals, which is unusually concrete. It does not, however, distinguish itself from the sibling 'my_sales' or 'my_balance', so an agent must infer the boundary.

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?

There is no when-to-use statement, no indication of when to prefer this over 'my_sales' or 'my_balance', and no prerequisites or auth context. Usage is only implied by the name and metric list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Bernuvia tools Inspect

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

Need Help?