Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

my_balance

YOUR MONEY (your owner's, which you administer but do not spend): the only one of the three account tools that returns FIGURES. Do NOT use it for your scopes or to find out what kind of credential you are: that is my_capabilities. Do NOT use it for your owner's profile data: that is my_profile. It returns the balance of YOUR OWNER's account (their in-app wallet, in ownerWallet, and whatever they have in escrow): it is read-only, you can neither withdraw nor spend it. The address YOU pay with goes in payerWallet, which is the canonical field and a 0x string; separately, agentWallet carries that same address WITH its USDC balance, which is what limits your purchases. canSell says whether TODAY you may sell with your owner's membership. The old names wallet and isSeller are still sent with the same values as DEPRECATED aliases (isSeller only says that your owner's role is not client, not that they can sell). payerWallet is NOT a deprecated alias: what changed was its type, from object to address.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
polWeiNoAgent account only: POL of its wallet in wei (it pays its own gas); null if it could not be read.
walletYesDEPRECATED ALIAS of `ownerWallet`, same value.
canSellYesIt can use the seller tools today.
gasNoteNoAgent account only: a reminder that it pays the gas itself.
isSellerYesDEPRECATED ALIAS: the account's role is not `client` (it decides whether the balance includes escrow).
accountTypeYesWhat kind of account is calling.
agentWalletNoOnly with a delegate: its paying wallet and the USDC balance that limits it.
ownerWalletYesWallet of the account being acted on (for a delegate, its owner's).
payerWalletYesThe wallet that ALWAYS pays (the delegate's when there is one).
availableUsdcYesAvailable right now (wallet plus what is claimable from escrow), in USDC.
walletOnlyUsdcYesOnly the wallet's USDC.
pendingReleaseUsdcYesCollected sales still in escrow, in USDC.
claimableEscrowUsdcYesClaimable from the current escrow; null when there is nothing to claim and the contract pays directly.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • changedOutput schema / properties / accountType / description
      Previous value: -"Qué clase de cuenta llama."New value: +"What kind of account is calling."
    • changedOutput schema / properties / agentWallet / description
      Previous value: -"Solo con delegado: su wallet pagadora y el saldo USDC que la limita."New value: +"Only with a delegate: its paying wallet and the USDC balance that limits it."
    • changedOutput schema / properties / agentWallet / properties / address / description
      Previous value: -"Dirección de la wallet del delegado."New value: +"Address of the delegate's wallet."
    • changedOutput schema / properties / agentWallet / properties / usdc / description
      Previous value: -"Saldo USDC de esa wallet; null si no se pudo leer."New value: +"USDC balance of that wallet; null if it could not be read."
    • changedOutput schema / properties / availableUsdc / description
      Previous value: -"Disponible ya mismo (wallet más lo reclamable del escrow), en USDC."New value: +"Available right now (wallet plus what is claimable from escrow), in USDC."
    • changedOutput schema / properties / canSell / description
      Previous value: -"Puede usar hoy las herramientas de vendedor."New value: +"It can use the seller tools today."
    • changedOutput schema / properties / claimableEscrowUsdc / description
      Previous value: -"Reclamable del escrow vigente; null cuando no hay nada que reclamar y el contrato paga directo."New value: +"Claimable from the current escrow; null when there is nothing to claim and the contract pays directly."
    • changedOutput schema / properties / gasNote / description
      Previous value: -"Solo cuenta-agente: recordatorio de que el gas lo paga ella."New value: +"Agent account only: a reminder that it pays the gas itself."
    • changedOutput schema / properties / isSeller / description
      Previous value: -"ALIAS RETIRADO: el rol de la cuenta no es `client` (decide si el saldo incluye la custodia)."New value: +"DEPRECATED ALIAS: the account's role is not `client` (it decides whether the balance includes escrow)."
    • changedOutput schema / properties / ownerWallet / description
      Previous value: -"Wallet de la cuenta sobre la que se actúa (para un delegado, la de su dueño)."New value: +"Wallet of the account being acted on (for a delegate, its owner's)."
    • changedOutput schema / properties / payerWallet / description
      Previous value: -"La wallet con la que se paga SIEMPRE (la del delegado cuando lo hay)."New value: +"The wallet that ALWAYS pays (the delegate's when there is one)."
    • changedOutput schema / properties / pendingReleaseUsdc / description
      Previous value: -"Ventas cobradas todavía en custodia, en USDC."New value: +"Collected sales still in escrow, in USDC."
    • changedOutput schema / properties / polWei / description
      Previous value: -"Solo cuenta-agente: POL de su wallet en wei (paga su propio gas); null si no se pudo leer."New value: +"Agent account only: POL of its wallet in wei (it pays its own gas); null if it could not be read."
    • changedOutput schema / properties / wallet / description
      Previous value: -"ALIAS RETIRADO de `ownerWallet`, mismo valor."New value: +"DEPRECATED ALIAS of `ownerWallet`, same value."
    • changedOutput schema / properties / walletOnlyUsdc / description
      Previous value: -"Solo el USDC de la wallet."New value: +"Only the wallet's USDC."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

No annotations are present, so the description carries the full disclosure burden. It states the tool is read-only, cannot withdraw/spend, clarifies owner vs agent wallet semantics, explains canSell as a daily sell eligibility flag, and warns about deprecated aliases wallet/isSeller. This goes well beyond what a bare schema would convey and contradicts nothing.

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

Conciseness3/5

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

The description is front-loaded with purpose and usage guidance and every section carries information, but it is verbose and somewhat redundant, for example restating read-only as 'you can neither withdraw nor spend it' and using emphatic caps that add noise. A tighter rewrite would preserve the useful details with less repetition.

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 zero-parameter read-only tool with an output schema, the description is complete: it identifies the owner vs agent distinction, spendability limits, deprecated aliases, and the correct sibling tools. No essential calling context appears to be 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?

There are zero input parameters, so the baseline is 4 and no input semantics are needed. The description instead adds meaning to returned fields such as ownerWallet, payerWallet, agentWallet, and canSell, which is useful despite not being input-parameter documentation.

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 states a specific verb and resource: it returns the balance/figures of the owner's account (wallet plus escrow). It differentiates itself from siblings by naming my_capabilities and my_profile as the tools for scopes and profile data, and by declaring it is the only account tool that returns figures.

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

Usage Guidelines5/5

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

It gives explicit exclusions and alternative routing: do not use for scopes/credential type (use my_capabilities) and do not use for owner profile data (use my_profile). The positive use case is implied clearly: use when you need wallet/escrow balance figures.

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