Skip to main content
Glama

register_wallet

[STATE] Register your wallet — the entry point for every tool that touches funds (Solana base58 pubkey for same-chain game + Shillbot; EVM 0x address for EVM/cross-chain). Non-custodial: keys never leave your device. Same-chain game_find_match works right after registration (landing deposit_stake proves ownership on-chain). Private Shillbot task tools, EVM/cross-chain queues, and the agent INBOX require wallet verification: sign the returned verify_nonce and call register_wallet AGAIN with {pubkey, nonce, signature} (base58 ed25519 for Solana — any ed25519 keypair works; 0x EIP-191 for EVM) or {pubkey, nonce, tx_signature} of an SPL-Memo tx for the higher tier. A passing proof returns verified: true + sender_tier in one call; agent_verify_wallet is the standalone equivalent. Messaging the team needs no proof (agent_send_message with no to_wallet). Idempotent; binding survives restarts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pubkey": "<pubkey>"
    },
    "name": "register_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
nonceNoOptional ownership proof, part 1: a nonce previously issued for this wallet (via agent_verify_wallet phase 1). When proof args are passed, verification runs BEFORE binding — a bad proof rejects without binding.
pubkeyYesBase58-encoded Solana public key (32 bytes). Non-custodial: only your public key is needed.
signatureNoOptional ownership proof, part 2a: signature over the nonce — base58 ed25519 for Solana wallets, 0x EIP-191 personal_sign for EVM wallets. Pass exactly one of `signature` / `tx_signature`.
tx_signatureNoOptional ownership proof, part 2b (Solana only): signature of a confirmed transaction that carries the nonce as an SPL-Memo.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that the wallet binding is non-custodial (keys never leave the device), that a passing proof returns verified: true plus sender_tier in one call, that bad proof args are validated before binding, and that the binding survives restarts. The one soft spot is the blanket 'Idempotent' claim, which sits in mild tension with idempotentHint=false; the text does elsewhere explain that a second call carrying proof args performs a distinct verification step.

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 entry point and the proof requirement are front-loaded and every sentence carries operational information; nothing is filler. It loses a point only because the middle section is a dense run-on that packs prerequisites, encodings, and tier rules into one paragraph, making it harder to scan than it needs to be.

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

Completeness4/5

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

With no output schema, the description still says what a successful verification returns (verified: true + sender_tier). It covers both registration modes, prerequisites, the no-proof messaging exception, persistence, and the sibling alternative. Only minor gaps remain, such as what the initial bare registration returns or how failures surface beyond 'rejects without binding'.

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 baseline is 3, but the description adds meaning not in the schema: which signature encoding applies to which chain (base58 ed25519 for Solana, any ed25519 keypair acceptable; 0x EIP-191 for EVM), and that tx_signature with an SPL-Memo earns the higher tier. That connects the four parameters to concrete outcomes rather than restating field text.

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+resource ('Register your wallet') and immediately frames its scope: 'the entry point for every tool that touches funds.' It also distinguishes wallet formats (Solana base58 vs EVM 0x) and names the standalone equivalent (agent_verify_wallet), so an agent can tell this apart from siblings without inspecting schemas.

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?

Explicit when-to-use guidance is given: same-chain game_find_match works right after registration; private Shillbot task tools, EVM/cross-chain queues, and the agent INBOX require the two-step signed-nonce flow; agent_send_message with no to_wallet needs no proof. It also names the alternative path (agent_verify_wallet as standalone equivalent) and the two proof tiers (ed25519/EIP-191 signature vs SPL-Memo tx_signature).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources