Skip to main content
Glama

Get My Wallet

get_my_wallet
Read-only

The caller's XP wallet: its address, whether one is connected (wallet_connected) and the USDC balance -- 'how much USDC do I have?'. That balance funds offers, buy_listing_now and buy_tickets with rail 'privy'. Requires sign-in and the read:account scope.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_my_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. Beyond that the description adds genuinely useful context: sign-in is required and the read:account scope is needed, and wallet_connected tells the caller whether an address exists. It does not say what happens when no wallet is connected (error vs. null balance), leaving a real behavioral gap for a low-annotation-burden read.

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?

Three front-loaded clauses: what it returns, what the balance is for, and what it requires to call. No filler sentences and no repetition of the tool name or title.

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?

An output schema exists, so return values need not be described, and the description still names the auth and scope prerequisites. The only omission is the unconnected-wallet behavior, which is the one thing an agent might need to handle the response correctly.

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 takes no parameters (0 required, 100% schema coverage), so there is nothing for the description to disambiguate and the baseline of 4 applies.

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?

States a specific resource (the caller's XP wallet) and the exact fields it returns: address, wallet_connected, and USDC balance, plus a natural-language anchor ('how much USDC do I have?'). That distinctly separates it from siblings such as get_user_account and get_my_orders.

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?

Gives clear context for when to reach for it: answering a balance question, and flagging that the balance is what funds offers, buy_listing_now and buy_tickets with rail 'privy'. It does not state exclusions (e.g., use get_user_account for profile data), so it stops short of full when/when-not guidance.

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