Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

seller_membership

The state of YOUR OWNER's seller membership (price, next charge, latest payments): you sell with it while it is in force. Activating it, changing it or cancelling it is your owner's business, from their browser and with their wallet; the link is for them, you cannot sign it. If it lapses, your seller tools stop answering.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
periodNoHow often it is charged.
statusYesState of this account's subscription.
canSellYesThe membership lets you sell today.
inGraceNoAgent account only: the membership is in grace because of a failed charge.
messageNoOnly with the membership turned off: that there is nothing to pay.
manageAtNoPeople only: the page where you sign with the wallet (the MCP never signs).
nextStepNoAgent account only: what to do now, with the right tool.
priceUsdcNoPrice of the membership in USDC, as a NUMBER (old form).
canceledAtNoWhen it was canceled (ISO).
graceUntilNoEnd of the grace window after a failed charge (ISO); it only exists while in grace.
lastPaymentsNoThe last 5 charges, from the most recent to the oldest.
nextChargeAtNoNext charge (ISO).
priceUsdcDecimalNoThe SAME price as a decimal string: the canonical form.
membershipEnabledYesThe platform requires a seller membership; false = you publish without paying anything.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed19 schema fields changed
    • changedOutput schema / properties / canSell / description
      Previous value: -"La membresía deja vender hoy."New value: +"The membership lets you sell today."
    • changedOutput schema / properties / canceledAt / description
      Previous value: -"Cuándo se canceló (ISO)."New value: +"When it was canceled (ISO)."
    • changedOutput schema / properties / graceUntil / description
      Previous value: -"Fin del margen tras un cobro fallido (ISO); solo existe estando en gracia."New value: +"End of the grace window after a failed charge (ISO); it only exists while in grace."
    • changedOutput schema / properties / inGrace / description
      Previous value: -"Solo cuenta-agente: la membresía está en gracia por un cobro fallido."New value: +"Agent account only: the membership is in grace because of a failed charge."
    • changedOutput schema / properties / lastPayments / description
      Previous value: -"Los 5 últimos cobros, del más reciente al más antiguo."New value: +"The last 5 charges, from the most recent to the oldest."
    • changedOutput schema / properties / lastPayments / items / properties / amountUsdc / description
      Previous value: -"Importe cobrado, en USDC."New value: +"Amount charged, in USDC."
    • changedOutput schema / properties / lastPayments / items / properties / date / description
      Previous value: -"Fecha del cobro (ISO)."New value: +"Date of the charge (ISO)."
    • changedOutput schema / properties / lastPayments / items / properties / status / description
      Previous value: -"Cómo acabó el cobro."New value: +"How the charge ended."
    • changedOutput schema / properties / manageAt / description
      Previous value: -"Solo para personas: la página donde se firma con la wallet (el MCP nunca firma)."New value: +"People only: the page where you sign with the wallet (the MCP never signs)."
    • changedOutput schema / properties / membershipEnabled / description
      Previous value: -"La plataforma exige membresía de vendedor; false = se publica sin pagar nada."New value: +"The platform requires a seller membership; false = you publish without paying anything."
    • changedOutput schema / properties / message / description
      Previous value: -"Solo con la membresía apagada: que no hay nada que pagar."New value: +"Only with the membership turned off: that there is nothing to pay."
    • changedOutput schema / properties / nextChargeAt / description
      Previous value: -"Próximo cobro (ISO)."New value: +"Next charge (ISO)."
    • changedOutput schema / properties / nextStep / description
      Previous value: -"Solo cuenta-agente: qué hacer ahora, con la herramienta que toca."New value: +"Agent account only: what to do now, with the right tool."
    • changedOutput schema / properties / period / description
      Previous value: -"Cada cuánto se cobra."New value: +"How often it is charged."
    • changedOutput schema / properties / period / properties / count / description
      Previous value: -"Cuántas unidades dura el ciclo."New value: +"How many units the cycle lasts."
    • changedOutput schema / properties / period / properties / unit / description
      Previous value: -"Unidad del ciclo: months o days."New value: +"Unit of the cycle: months or days."
    • changedOutput schema / properties / priceUsdc / description
      Previous value: -"Precio de la membresía en USDC, como NÚMERO (forma antigua)."New value: +"Price of the membership in USDC, as a NUMBER (old form)."
    • changedOutput schema / 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 / status / description
      Previous value: -"Estado de la suscripción de esta cuenta."New value: +"State of this account's subscription."
  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 behavioral disclosure burden. It does well by disclosing that the membership link is for the owner, that the agent cannot sign it, and that a lapsed membership causes seller tools to stop answering. It stops short of explicitly stating 'this operation is read-only and has no side effects,' though that is strongly implied.

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 three sentences, each earning its place: what the tool reports, who can perform membership actions, and the consequence of lapse. It is front-loaded with the core meaning and contains no filler.

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

Completeness5/5

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

For a parameterless informational tool with an output schema present, the description covers the essential context: membership state fields, ownership boundaries, agent limitations, and operational consequences. Nothing needed to correctly invoke this tool is missing.

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 tool has zero parameters, so the schema is trivially complete and there is nothing for the description to clarify. The baseline for zero parameters is 4, and the description does not need to add parameter-level information.

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 clearly identifies the resource as the owner's seller membership and specifies the kind of information returned (price, next charge, latest payments). It does not use an explicit verb like 'retrieves' or 'checks', but the noun phrase 'The state of...' strongly implies a read-only status query and the description distinguishes this from membership management actions.

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 gives clear context for when to use this tool: to know the seller membership state that governs selling activity. It also explicitly says activation, changing, or cancellation is not this tool's business and cannot be signed by the agent, which is an effective exclusion. It doesn't name a specific alternative tool, but given the zero-parameter informational nature, that is acceptable.

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