Skip to main content
Glama

get_wallet_address

Retrieve your Solana wallet address to receive USDC funds or share for blockchain transactions on devnet.

Instructions

Get the agent's Solana wallet address. Use this to receive funds or share your address.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:26-33 (registration)
    Registration of the 'get_wallet_address' tool in the TOOLS array, including name, description, and input schema.
      name: "get_wallet_address",
      description: "Get the agent's Solana wallet address. Use this to receive funds or share your address.",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • Input schema definition for the 'get_wallet_address' tool (empty object, no parameters).
    inputSchema: {
      type: "object",
      properties: {},
      required: [],
    },
  • MCP tool handler for 'get_wallet_address': retrieves wallet address via AgentWallet and returns formatted JSON response with explorer link.
    case "get_wallet_address": {
      const address = wallet.getAddress();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              address,
              network: "devnet",
              explorer: `https://explorer.solana.com/address/${address}?cluster=devnet`,
            }, null, 2),
          },
        ],
      };
    }
  • Core helper method in AgentWallet class that returns the Solana public key as base58 string.
    getAddress(): string {
      return this.keypair.publicKey.toBase58();
    }
Behavior3/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. It implies a read-only operation by using 'Get' and hints at use cases, but does not detail potential errors, authentication needs, or rate limits. This is adequate but lacks depth for a tool in a financial context.

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?

The description is two sentences, front-loaded with the core purpose and followed by a usage guideline. Every word earns its place, with no wasted text, making it highly efficient and easy to parse.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is reasonably complete. It explains what the tool does and when to use it. However, it could benefit from more behavioral context, such as error handling or return format, to achieve a score of 5.

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 input schema has 0 parameters with 100% coverage, so the schema fully documents the lack of inputs. The description does not need to add parameter details, and it appropriately focuses on the tool's purpose without redundancy. A baseline of 4 is applied for zero-parameter tools.

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 specific action ('Get') and resource ('agent's Solana wallet address'), distinguishing it from sibling tools like get_balance or get_recent_transactions. It provides a concrete purpose that is immediately understandable and differentiated.

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 explicitly states when to use this tool ('to receive funds or share your address'), providing clear context for its application. However, it does not mention when not to use it or explicitly compare it to alternatives like send_usdc, which would be needed for a score of 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/noah-ing/agent-wallet-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server