Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

my_cart

Returns the account's cart.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesThe cart items, in the order they were saved.
slugsYesThe saved slugs, exactly as they are in the database.
totalYesHow many lines the cart has.
totalUsdcYesSum in USDC of ONLY what can be bought, as a NUMBER (old form, kept).
totalUsdcDecimalYesThe SAME sum as a decimal string with two decimals: the canonical form of every amount (section 15.1).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • changedOutput schema / properties / items / description
      Previous value: -"Los artículos del carrito, en el orden guardado."New value: +"The cart items, in the order they were saved."
    • changedOutput schema / properties / items / items / properties / available / description
      Previous value: -"Sigue a la venta y se puede pagar."New value: +"Still on sale and can be paid for."
    • changedOutput schema / properties / items / items / properties / category / description
      Previous value: -"Categoría de la plantilla."New value: +"Category of the template."
    • changedOutput schema / properties / items / items / properties / compareAtUsdc / description
      Previous value: -"Precio tachado en USDC como NÚMERO (forma antigua, se conserva)."New value: +"Struck through price in USDC as a NUMBER (old form, kept)."
    • changedOutput schema / properties / items / items / properties / compareAtUsdcDecimal / description
      Previous value: -"El MISMO precio tachado como cadena decimal."New value: +"The SAME struck through price as a decimal string."
    • changedOutput schema / properties / items / items / properties / image / description
      Previous value: -"Portada o primera imagen de la galería."New value: +"Cover image, or the first image of the gallery."
    • changedOutput schema / properties / items / items / properties / name / description
      Previous value: -"Nombre traducido (o el slug si ya no existe)."New value: +"Translated name (or the slug if it no longer exists)."
    • changedOutput schema / properties / items / items / properties / priceUsdc / description
      Previous value: -"Precio en USDC como NÚMERO (forma antigua, se conserva); null si no está a la venta."New value: +"Price in USDC as a NUMBER (old form, kept); null if it is not on sale."
    • changedOutput schema / properties / items / items / properties / priceUsdcDecimal / description
      Previous value: -"El MISMO precio como cadena decimal: la forma canónica."New value: +"The SAME price as a decimal string: the canonical form."
    • changedOutput schema / properties / items / items / properties / slug / description
      Previous value: -"Slug de la plantilla."New value: +"Slug of the template."
    • changedOutput schema / properties / slugs / description
      Previous value: -"Los slugs guardados, tal cual están en la base."New value: +"The saved slugs, exactly as they are in the database."
    • changedOutput schema / properties / total / description
      Previous value: -"Cuántas líneas hay en el carrito."New value: +"How many lines the cart has."
    • changedOutput schema / properties / totalUsdc / description
      Previous value: -"Suma en USDC de SOLO lo comprable, como NÚMERO (forma antigua, se conserva)."New value: +"Sum in USDC of ONLY what can be bought, as a NUMBER (old form, kept)."
    • changedOutput schema / properties / totalUsdcDecimal / description
      Previous value: -"La MISMA suma como cadena decimal con dos decimales: la forma canónica de todo importe (sección 15.1)."New value: +"The SAME sum as a decimal string with two decimals: the canonical form of every amount (section 15.1)."
  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 conveys read-only intent through 'Returns' and account scoping, which is useful, but it does not disclose auth requirements, error behavior, or whether a nonexistent cart is auto-created. There is no contradiction with annotations.

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?

A single, front-loaded sentence with no filler: 'Returns the account's cart.' Every word contributes to the operation and resource scope, making it maximally concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With zero parameters and an output schema present, the description does not need to explain return shape. However, it still lacks usage guidance and behavioral caveats such as auth or side-effect behavior, making it adequate but not fully complete.

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?

The input schema has zero properties and schema description coverage is 100%, so there are no parameter semantics to document. The baseline score of 4 applies because no parameter explanation is needed.

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 uses the specific verb 'Returns' with a clear resource, 'the account's cart,' so the core operation is unmistakable. It does not explicitly differentiate from siblings like my_purchases or my_draft, but 'cart' is a distinct resource and the read intent is clear.

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?

The retrieval intent is implied by the verb 'Returns,' but the description does not explicitly say when to use this tool versus cart-mutating siblings like add_to_cart or remove_from_cart. There is no when-not-to-use guidance or alternative routing.

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