Skip to main content
Glama
minhoyoo-iotrust

waiaas

by minhoyoo-iotrust
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

get_address

Retrieve the public address of a cryptocurrency wallet to enable transactions, interactions, and balance checks across supported blockchain networks.

Instructions

Get the public address of the wallet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wallet_idNoTarget wallet ID. Required for multi-wallet sessions; auto-resolved when session has a single wallet.

Implementation Reference

  • packages/mcp/src/tools/get-address.ts:17-23 (handler)
    The handler function for the get_address MCP tool, which makes an API call to /v1/wallet/address.
    async (args) => {
  const params = new URLSearchParams();
  if (args.wallet_id) params.set('walletId', args.wallet_id);
  const qs = params.toString();
  const result = await apiClient.get('/v1/wallet/address' + (qs ? '?' + qs : ''));
  return toToolResult(result);
},
  • packages/mcp/src/tools/get-address.ts:10-25 (registration)
    The registration function that defines the 'get_address' tool and its parameters for the McpServer.
    export function registerGetAddress(server: McpServer, apiClient: ApiClient, walletContext?: WalletContext): void {
  server.tool(
    'get_address',
    withWalletPrefix('Get the public address of the wallet.', walletContext?.walletName),
    {
      wallet_id: z.string().optional().describe('Target wallet ID. Required for multi-wallet sessions; auto-resolved when session has a single wallet.'),
    },
    async (args) => {
      const params = new URLSearchParams();
      if (args.wallet_id) params.set('walletId', args.wallet_id);
      const qs = params.toString();
      const result = await apiClient.get('/v1/wallet/address' + (qs ? '?' + qs : ''));
      return toToolResult(result);
    },
  );
}

Tool Definition Quality

C2.9/5.0
Behavior2/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. While specifying 'public' correctly signals this is a safe read operation (not exposing private keys), it omits critical details: the return format (checksummed hex? case sensitivity?), whether this performs an RPC call or local lookup, validation behavior for invalid wallet_ids, and whether the result is cached.

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 consists of a single, efficient sentence (9 words) that is front-loaded with the action verb. While extremely terse, there is no redundant or wasted language. However, the brevity comes at the cost of omitting useful contextual details that would justify additional sentences.

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

Completeness3/5

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

For a simple, single-parameter getter tool with complete schema documentation, the description is minimally viable. It identifies what is retrieved but fails to specify the output format (critical for blockchain addresses) or address type (e.g., EOA vs. contract). Without an output schema, the description should have indicated the return value structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the parameter `wallet_id` is fully documented within the schema itself. The description adds no specific parameter semantics, but given the high schema coverage, it does not need to compensate. It neither clarifies nor contradicts the schema's explanation of when the parameter is required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Get') and clearly identifies the resource ('public address' of the wallet). It distinguishes the address from private keys via the 'public' modifier. However, it fails to explicitly differentiate from sibling tool `get_wallet_info`, which could create ambiguity about which tool returns the address versus general wallet metadata.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like `get_wallet_info` or `connect_info`. It does not mention prerequisites (e.g., session requirements) or when the wallet_id parameter is necessary versus optional, despite the schema indicating conditional requirement.

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/minhoyoo-iotrust/WAIaaS'

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