Skip to main content
Glama
getpara
by getpara

get_wallet

Retrieve wallet details including status, address, and public key by providing the wallet ID. This tool enables AI agents to access and manage wallet information across multiple blockchain networks.

Instructions

Get wallet details by ID, including status, address, and public key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
walletIdYesThe wallet ID returned from create_wallet

Implementation Reference

  • The handler function for 'get_wallet' that fetches wallet details from the API.
    export async function handler(client: ParaClient, args: Record<string, unknown>) {
      const walletId = args.walletId as string;
    
      const wallet = await client.requestWithRetry<Wallet>(`/v1/wallets/${walletId}`);
    
      return {
        content: [
          {
            type: 'text' as const,
            text: JSON.stringify(wallet, null, 2),
          },
        ],
      };
    }
  • The definition and input schema for the 'get_wallet' tool.
    export const definition = {
      name: 'get_wallet',
      description: 'Get wallet details by ID, including status, address, and public key.',
      inputSchema: {
        type: 'object' as const,
        properties: {
          walletId: {
            type: 'string',
            description: 'The wallet ID returned from create_wallet',
          },
        },
        required: ['walletId'],
      },
    };
Behavior2/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 states it 'Get[s] wallet details', implying a read-only operation, but does not disclose behavioral traits such as required permissions, error handling, rate limits, or what happens if the wallet ID is invalid. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 concise and front-loaded in a single sentence, efficiently stating the tool's purpose and key details without unnecessary words. Every part of the sentence contributes to understanding, making it well-structured and easy to parse.

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?

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is somewhat complete but lacks depth. It covers the basic purpose and parameter source, but without annotations or output schema, it should ideally include more on behavior, error cases, or return format to be fully helpful. It meets minimum viability but has clear gaps.

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?

The schema description coverage is 100%, with the parameter 'walletId' well-documented in the schema. The description adds minimal value beyond the schema by mentioning the ID comes from 'create_wallet', but does not provide additional semantics like format constraints or examples. Baseline 3 is appropriate as the schema handles most of the parameter documentation.

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 clearly states the tool's purpose with a specific verb ('Get') and resource ('wallet details'), specifying what information is retrieved (status, address, and public key). However, it does not explicitly differentiate from sibling tools like 'list_wallets', which might retrieve multiple wallets, leaving some ambiguity.

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. It mentions the wallet ID comes from 'create_wallet', but does not specify if this is for single-wallet retrieval after creation, or how it differs from 'list_wallets' for browsing wallets. No explicit when/when-not or alternative usage is stated.

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/getpara/para-wallet-mcp'

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