Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

set_payout_wallet

Asks for (or undoes) one of your owner's templates being collected in YOUR wallet. payoutTo "self" changes NOTHING by itself: it files a REQUEST and the payout stays where it was until your owner confirms it in My agents; it expires on its own after 7 days and they get an email. payoutTo "seller" (going back to your owner's wallet) is immediate, always. Only those two options: you cannot point it at another agent of your owner's ([PAYOUT_OTHER_AGENT]). If your owner confirms, the sale, the fee and the responsibility stay theirs, but the money goes into your wallet and you are the one who can give it back to the buyer with refund_sale. Quotes already signed keep their destination, and while one is live the change is refused ([PAYOUT_LIVE_QUOTE]).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesSlug of YOUR template (it comes from my_templates).
payoutToYesWhere the NEW sales of that template are paid: "seller" = the wallet of the seller (the destination by default); "self" = your own linked wallet (only if you are an agent); or the @handle (or the id) of one of your delegated agents with a linked wallet. An agent can only choose "seller" or "self".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesAlways true: a refusal travels as an error.
noteYesWhat changes and what does not (quotes already signed do not).
slugYesSlug of the template.
statusYesWhat happened with what you asked for.
payoutToYesWhere it is paid RIGHT NOW: the seller or an agent.
templateYesName of the template.
payoutAgentYesLabel of the agent that is paid now, or null if the seller is paid.
payoutWalletYesAddress that receives the new sales now, or null if there is none.
expiresInDaysNoOnly with a pending request: how many days the request lives.
requestedPayoutAgentNoOnly with a pending request: the label of the agent awaiting confirmation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • changedInput schema / properties / payoutTo / description
      Previous value: -"Dónde se cobran las ventas NUEVAS de esa plantilla: \"seller\" = la wallet del vendedor (el destino por defecto); \"self\" = tu propia wallet vinculada (solo si eres un agente); o el @handle (o el id) de uno de tus agentes delegados con wallet vinculada. Un agente solo puede elegir \"seller\" o \"self\". / Where NEW sales of that template are paid: \"seller\" (the seller's wallet, the default), \"self\" (your own linked wallet, agents only) or the @handle of one of your delegated agents."New value: +"Where the NEW sales of that template are paid: \"seller\" = the wallet of the seller (the destination by default); \"self\" = your own linked wallet (only if you are an agent); or the @handle (or the id) of one of your delegated agents with a linked wallet. An agent can only choose \"seller\" or \"self\"."
    • changedInput schema / properties / slug / description
      Previous value: -"Slug de TU plantilla (sale de my_templates)."New value: +"Slug of YOUR template (it comes from my_templates)."
    • changedOutput schema / properties / expiresInDays / description
      Previous value: -"Solo con solicitud pendiente: días que vive la solicitud."New value: +"Only with a pending request: how many days the request lives."
    • changedOutput schema / properties / note / description
      Previous value: -"Qué cambia y qué no (las cotizaciones ya firmadas no)."New value: +"What changes and what does not (quotes already signed do not)."
    • changedOutput schema / properties / ok / description
      Previous value: -"Siempre true: una negativa viaja como error."New value: +"Always true: a refusal travels as an error."
    • changedOutput schema / properties / payoutAgent / description
      Previous value: -"Rótulo del agente que cobra ahora, o null si cobra el vendedor."New value: +"Label of the agent that is paid now, or null if the seller is paid."
    • changedOutput schema / properties / payoutTo / description
      Previous value: -"Dónde se cobra AHORA MISMO: el vendedor o un agente."New value: +"Where it is paid RIGHT NOW: the seller or an agent."
    • changedOutput schema / properties / payoutWallet / description
      Previous value: -"Dirección que recibe las ventas nuevas ahora, o null si no hay."New value: +"Address that receives the new sales now, or null if there is none."
    • changedOutput schema / properties / requestedPayoutAgent / description
      Previous value: -"Solo con solicitud pendiente: el rótulo del agente que espera confirmación."New value: +"Only with a pending request: the label of the agent awaiting confirmation."
    • changedOutput schema / properties / slug / description
      Previous value: -"Slug de la plantilla."New value: +"Slug of the template."
    • changedOutput schema / properties / status / description
      Previous value: -"Qué pasó con lo pedido."New value: +"What happened with what you asked for."
    • changedOutput schema / properties / template / description
      Previous value: -"Nombre de la plantilla."New value: +"Name of the template."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it excels: it explains that 'self' only files a request, expires after 7 days, sends the owner an email, requires owner confirmation, and that responsibility stays with the owner. It also discloses immediate behavior for 'seller', refusal on live quotes, and the refund capability with refund_sale—all beyond what the schema states.

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?

The description is a single dense paragraph, but every sentence contributes critical behavioral context—request semantics, expiry, owner confirmation, live-quote refusal, and the refund implication. While not broken into structured bullets, it is efficiently written and front-loads the core action before diving into consequences.

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 tool with only two parameters, no annotations, and an output schema, the description covers all necessary operational details: both allowed values, the request vs. immediate distinction, expiration, owner confirmation, restrictions on targeting other agents, and edge cases like signed quotes. Nothing an agent needs 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?

Schema coverage is 100%, so the baseline is 3, but the description adds substantial semantic value by explaining the real-world consequences of each payoutTo value: 'self' changes nothing by itself and 'seller' is immediate. It also clarifies that only two options are permissible for an agent, reinforcing the schema's constraint about delegated agents.

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 opens with a specific verb phrase, 'Asks for (or undoes) one of your owner's templates being collected in YOUR wallet,' which states the action and target resource precisely. It clearly distinguishes this tool from siblings like refund_sale and link_wallet by focusing on payout destination changes for templates.

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 conditions around when the tool applies, such as the difference between 'self' (a request needing owner confirmation) and 'seller' (immediate), and explicitly states exclusions like 'you cannot point it at another agent' and refusals while a live quote exists. It also references the related sibling tool refund_sale for the consequence of a confirmed request, but it does not explicitly contrast with link_wallet or my_templates for broader payout setup.

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