Skip to main content
Glama
matteoantoci

MCP Bitpanda Server

list_fiat_wallets

Retrieve all fiat currency wallets from Bitpanda to view balances and manage traditional currency holdings.

Instructions

Lists all user's fiat wallets from the Bitpanda API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the tool logic by fetching fiat wallets from the Bitpanda API using axios.
    const listFiatWalletsHandler = async (_input: Input): Promise<Output> => {
      try {
        const apiKey = getBitpandaApiKey();
        const url = `${BITPANDA_API_BASE_URL}/fiatwallets`;
    
        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 fiat wallets:', error);
        const message = error instanceof Error ? error.message : 'An unknown error occurred while fetching fiat wallets.';
        // Re-throwing the error to be handled by the MCP server framework
        throw new Error(`Failed to fetch Bitpanda fiat wallets: ${message}`);
      }
    };
  • Defines the input schema (empty object) and TypeScript types for input and output of the list_fiat_wallets tool.
    // Define the input schema shape for the list_fiat_wallets tool (no parameters)
    const listFiatWalletsInputSchemaShape = {};
    
    type RawSchemaShape = typeof listFiatWalletsInputSchemaShape;
    type Input = z.infer<z.ZodObject<RawSchemaShape>>;
    // Define the expected output structure based on the API documentation
    type Output = {
      data: Array<{
        type: string;
        attributes: {
          fiat_id: string;
          fiat_symbol: string;
          balance: string;
          name: string;
          pending_transactions_count: number;
        };
        id: string;
      }>;
    };
  • Exports the complete tool definition for list_fiat_wallets, bundling name, description, schema, and handler.
    export const listFiatWalletsTool: BitpandaToolDefinition = {
      name: 'list_fiat_wallets',
      description: "Lists all user's fiat wallets from the Bitpanda API.",
      inputSchemaShape: listFiatWalletsInputSchemaShape,
      handler: listFiatWalletsHandler,
    };
  • Registers the list_fiat_wallets tool (among others) with the MCP server using server.tool().
    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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a list operation, implying it's likely read-only, but doesn't confirm this or add any other behavioral context such as authentication requirements, rate limits, pagination, or what happens if no wallets exist. This leaves significant gaps for a tool interacting with an external API.

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, direct sentence that efficiently conveys the core purpose without any fluff or redundancy. It's appropriately sized and front-loaded, 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's simplicity (0 parameters, no output schema, no annotations), the description is adequate but not complete. It specifies the resource type ('fiat wallets') and source ('Bitpanda API'), which is helpful, but lacks behavioral details like authentication needs or response format, which are important for API tools. The absence of an output schema increases the need for more context in the description.

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 tool has 0 parameters, and the schema description coverage is 100% (though empty). The description doesn't need to add parameter semantics, so it meets the baseline expectation. It appropriately doesn't discuss parameters, avoiding unnecessary detail.

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 verb ('Lists') and resource ('all user's fiat wallets from the Bitpanda API'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_crypto_wallets' or 'list_asset_wallets', which would require mentioning it specifically retrieves fiat (not crypto or asset) wallets.

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 doesn't mention sibling tools like 'list_crypto_wallets' or 'list_asset_wallets', nor does it specify prerequisites, contexts, or exclusions for its use.

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