Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

link_wallet

Links YOUR OWN wallet (the agent's, never your owner's in-app wallet) with proof of control: you sign a challenge, no gas. IT CAN ONLY BE DONE ONCE: an agent account never changes its wallet, and the only way out is to create another agent. You act as your owner, but you pay with this wallet: it stays as the paying wallet of the purchases you make in their name, and their refunds come back to it. It can also COLLECT the sales of the templates that you (or your owner) assign to it with set_payout_wallet, and then you are the one who signs their refund with refund_sale. It never withdraws your owner's money.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
firmaNoDEPRECATED alias of `signature`: it still works, but use `signature` (it will be removed in a future round, no date yet). personal_sign signature of the `mensaje` from step 1, made with that wallet.
nonceNoThe nonce returned in step 1 (omit it to request the challenge).
walletYesThe agent's EOA address (0x + 40 hex).
signatureNopersonal_sign signature of the `mensaje` from step 1, made with that wallet.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNoOnly when linking: true if the wallet was linked.
notaNoOnly when linking: a text clarification of the result.
pasoNoOnly in the challenge (step 1): its value is "firmar". Absent when linking.
nonceNoOnly in the challenge: the nonce you have to send back together with the signature. It expires in 10 minutes.
walletNoOnly when linking: the linked address, in checksum format (EIP-55).
mensajeNoOnly in the challenge: the exact text you have to sign with personal_sign.
instruccionesNoOnly in the challenge: what to do with `mensaje` and `nonce`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • changedInput schema / properties / firma / description
      Previous value: -"ALIAS RETIRADO de `signature`: sigue funcionando, pero usa `signature` (se quitará en una tanda futura, aún sin fecha). / DEPRECATED alias of `signature`. Firma personal_sign del `mensaje` del paso 1, hecha con esa wallet."New value: +"DEPRECATED alias of `signature`: it still works, but use `signature` (it will be removed in a future round, no date yet). personal_sign signature of the `mensaje` from step 1, made with that wallet."
    • changedInput schema / properties / nonce / description
      Previous value: -"El nonce devuelto en el paso 1 (omítelo para pedir el reto)."New value: +"The nonce returned in step 1 (omit it to request the challenge)."
    • changedInput schema / properties / signature / description
      Previous value: -"Firma personal_sign del `mensaje` del paso 1, hecha con esa wallet."New value: +"personal_sign signature of the `mensaje` from step 1, made with that wallet."
    • changedInput schema / properties / wallet / description
      Previous value: -"Dirección EOA del agente (0x + 40 hex)."New value: +"The agent's EOA address (0x + 40 hex)."
    • changedOutput schema / properties / instrucciones / description
      Previous value: -"Solo en el reto: qué hacer con `mensaje` y `nonce`."New value: +"Only in the challenge: what to do with `mensaje` and `nonce`."
    • changedOutput schema / properties / mensaje / description
      Previous value: -"Solo en el reto: el texto exacto que hay que firmar con personal_sign."New value: +"Only in the challenge: the exact text you have to sign with personal_sign."
    • changedOutput schema / properties / nonce / description
      Previous value: -"Solo en el reto: el nonce que hay que devolver junto con la firma. Caduca en 10 minutos."New value: +"Only in the challenge: the nonce you have to send back together with the signature. It expires in 10 minutes."
    • changedOutput schema / properties / nota / description
      Previous value: -"Solo al vincular: aclaración en texto del resultado."New value: +"Only when linking: a text clarification of the result."
    • changedOutput schema / properties / ok / description
      Previous value: -"Solo al vincular: true si la wallet quedó vinculada."New value: +"Only when linking: true if the wallet was linked."
    • changedOutput schema / properties / paso / description
      Previous value: -"Solo en el reto (paso 1): vale \"firmar\". Ausente al vincular."New value: +"Only in the challenge (step 1): its value is \"firmar\". Absent when linking."
    • changedOutput schema / properties / wallet / description
      Previous value: -"Solo al vincular: la dirección vinculada, en formato checksum (EIP-55)."New value: +"Only when linking: the linked address, in checksum format (EIP-55)."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses the one-time irreversible nature, the fact that it never withdraws the owner's money, the signing flow (challenge, no gas), and the downstream consequences for payments and refunds. This is rich behavioral context beyond what the schema shows.

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 dense and front-loaded with the most important constraint (one-time, own wallet). Every sentence adds information, though the capitalization and run-on structure make it slightly harder to parse. It's longer than ideal but each clause earns its place.

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?

The description covers the purpose, the one-time constraint, the payment/refund implications, the relationship to sibling tools, and the safety guarantee. With an output schema present and 100% parameter coverage, nothing critical is missing for an agent to decide whether and how to call this tool.

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. The description adds context about the two-step challenge flow (nonce from step 1, signature of the mensaje), which clarifies how the parameters relate to each other. It doesn't add syntax details beyond the schema, but the flow explanation adds meaningful value.

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 clearly states the tool links the agent's own wallet via a signed challenge, with no gas. It explicitly distinguishes from the owner's in-app wallet and names the one-time constraint. The verb 'links' plus the resource 'wallet' and the proof-of-control mechanism make the purpose unmistakable.

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?

The description explicitly says it can only be done once, that the wallet becomes the paying wallet for purchases and collects sales, and that the only way out is creating another agent. It also references sibling tools set_payout_wallet and refund_sale, giving clear context for when this tool is relevant.

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