Skip to main content
Glama
matteoantoci

MCP Bitpanda Server

list_asset_wallets

Retrieve all cryptocurrency wallets grouped by asset type from your Bitpanda account to view holdings and manage portfolio distribution.

Instructions

Lists all user's asset wallets grouped by asset type from the Bitpanda API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the list_asset_wallets tool. It fetches the user's asset wallets from the Bitpanda API using axios.get on /asset-wallets endpoint.
    const listAssetWalletsHandler = async (_input: Input): Promise<Output> => {
      try {
        const apiKey = getBitpandaApiKey();
        const url = `${BITPANDA_API_BASE_URL}/asset-wallets`;
    
        const response = await axios.get<Output>(url, {
          headers: {
            'X-Api-Key': apiKey,
            'Content-Type': 'application/json',
          },
        });
    
        // Return the data received from the Bitpanda API
        return response.data;
      } catch (error: unknown) {
        console.error('Error fetching Bitpanda asset wallets:', error);
        const message = error instanceof Error ? error.message : 'An unknown error occurred while fetching asset wallets.';
        // Re-throwing the error to be handled by the MCP server framework
        throw new Error(`Failed to fetch Bitpanda asset wallets: ${message}`);
      }
    };
  • Input schema and types for the list_asset_wallets tool (no input parameters required).
    // Define the input schema shape for the list_asset_wallets tool (no parameters)
    const listAssetWalletsInputSchemaShape = {};
    
    type RawSchemaShape = typeof listAssetWalletsInputSchemaShape;
    type Input = z.infer<z.ZodObject<RawSchemaShape>>;
  • Tool definition export for list_asset_wallets, including name, description, schema, and handler reference.
    export const listAssetWalletsTool: BitpandaToolDefinition = {
      name: 'list_asset_wallets',
      description: "Lists all user's asset wallets grouped by asset type from the Bitpanda API.",
      inputSchemaShape: listAssetWalletsInputSchemaShape,
      handler: listAssetWalletsHandler,
    };
  • Function that registers all tools, including list_asset_wallets, with the MCP server by calling server.tool() for each.
    export const registerBitpandaTools = (server: McpServer): void => {
      bitpandaToolDefinitions.forEach((toolDef) => {
        try {
          // Pass the raw shape to the inputSchema parameter, assuming SDK handles z.object()
          server.tool(toolDef.name, toolDef.description, toolDef.inputSchemaShape, async (input) => {
            const result = await toolDef.handler(input);
            // Assuming the handler returns the data directly, wrap it in the MCP content format
            return {
              content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
            };
          });
          console.log(`Registered Bitpanda tool: ${toolDef.name}`);
        } catch (error) {
          console.error(`Failed to register tool ${toolDef.name}:`, error);
        }
      });
    };
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 of behavioral disclosure. It states this is a list operation, implying it's likely read-only and non-destructive, but doesn't confirm this or address other traits like authentication needs, rate limits, or response format. The description adds minimal behavioral context beyond the basic action.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 has no parameters and no output schema, the description is minimally adequate by stating what it does. However, as a list operation with sibling tools that might overlap (e.g., 'list_crypto_wallets'), it lacks context on scope or differentiation, and without annotations, it doesn't address behavioral aspects like safety or response format, leaving gaps for the agent.

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 no parameter documentation is needed. The description appropriately doesn't discuss parameters, and the baseline for this scenario is 4, as it avoids redundancy while being complete for a parameterless tool.

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 action ('Lists') and resource ('user's asset wallets grouped by asset type from the Bitpanda API'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_crypto_wallets' or 'list_fiat_wallets', which appear to be more specific versions of this tool.

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 'list_crypto_wallets' or 'list_fiat_wallets'. It doesn't mention prerequisites, exclusions, or comparative contexts, leaving the agent to infer usage from tool names alone.

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/matteoantoci/mcp-bitpanda'

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