Skip to main content
Glama
getpara
by getpara

list_wallets

Fetch multiple Para MPC wallets simultaneously by their IDs to retrieve wallet data across EVM, Solana, and Cosmos blockchains. Handles up to 10 wallet IDs per request.

Instructions

Batch-fetch multiple wallets by their IDs. Para has no native list endpoint, so this fetches each wallet individually via Promise.allSettled. Maximum 10 IDs per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
walletIdsYesArray of wallet IDs to fetch (max 10)

Implementation Reference

  • The handler function that executes the list_wallets tool logic by fetching multiple wallets via their IDs.
    export async function handler(client: ParaClient, args: Record<string, unknown>) {
      const walletIds = args.walletIds as string[];
    
      if (!Array.isArray(walletIds) || walletIds.length === 0) {
        return {
          content: [{ type: 'text' as const, text: 'Error: walletIds must be a non-empty array.' }],
          isError: true,
        };
      }
    
      if (walletIds.length > 10) {
        return {
          content: [{ type: 'text' as const, text: 'Error: Maximum 10 wallet IDs per call.' }],
          isError: true,
        };
      }
    
      const results = await Promise.allSettled(
        walletIds.map((id) => client.requestWithRetry<Wallet>(`/v1/wallets/${id}`)),
      );
    
      const wallets = results.map((result, i) => {
        if (result.status === 'fulfilled') {
          return { walletId: walletIds[i], ...result.value };
        }
        return {
          walletId: walletIds[i],
          error: result.reason instanceof Error ? result.reason.message : String(result.reason),
        };
      });
    
      return {
        content: [
          {
            type: 'text' as const,
            text: JSON.stringify({ wallets }, null, 2),
          },
        ],
      };
    }
  • The schema definition for the list_wallets tool, including input validation.
    export const definition = {
      name: 'list_wallets',
      description:
        'Batch-fetch multiple wallets by their IDs. Para has no native list endpoint, so this fetches each wallet individually via Promise.allSettled. Maximum 10 IDs per call.',
      inputSchema: {
        type: 'object' as const,
        properties: {
          walletIds: {
            type: 'array',
            items: { type: 'string' },
            description: 'Array of wallet IDs to fetch (max 10)',
          },
        },
        required: ['walletIds'],
      },
    };
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well by disclosing key behavioral traits: it's a read operation (fetch), uses Promise.allSettled for individual calls, has a rate limit (max 10 IDs), and explains the implementation workaround. It doesn't mention error handling or response format details.

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 perfectly concise with three sentences that each earn their place: states purpose, explains implementation rationale, and specifies constraints. It's front-loaded with the core functionality and wastes no words.

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?

For a tool with no annotations and no output schema, the description does well by covering purpose, implementation, and constraints. However, it lacks details about the return format (e.g., structure of results from Promise.allSettled) and error handling, which would be helpful given the complexity of batch operations.

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?

Schema description coverage is 100%, so the schema already documents the 'walletIds' parameter fully. The description adds minimal value by restating the max 10 limit but doesn't provide additional semantics like ID format examples or validation rules beyond what the schema implies.

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 ('Batch-fetch multiple wallets by their IDs') and distinguishes it from siblings like 'get_wallet' (singular fetch) and 'create_wallet'. It explains this is a workaround for Para's lack of a native list endpoint.

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 provides clear context about when to use this tool (when needing multiple wallets, up to 10 IDs) and implies an alternative (using 'get_wallet' for single wallets). However, it doesn't explicitly state when NOT to use it or compare it to all siblings like 'sign_raw' or 'wait_for_wallet_ready'.

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