Skip to main content
Glama
blaze-xyz
by blaze-xyz

list_fundings

Retrieve funding transaction records from the Bitso cryptocurrency exchange to monitor deposits and track account balance changes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Executes the list_fundings tool: parses input params with Zod schema, fetches fundings via BitsoApiClient.getFundings(), formats and returns JSON response or error message.
        try {
          const validatedParams = ListFundingsSchema.parse(params);
          logToFile('INFO', 'List fundings tool called', validatedParams);
          
          const response = await client.getFundings(validatedParams);
          
          if (!response.success || !response.payload || response.payload.length === 0) {
            return {
              content: [
                {
                  type: "text",
                  text: "No fundings found with the specified criteria."
                }
              ]
            };
          }
          
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify({
                  success: true,
                  count: response.payload.length,
                  fundings: response.payload.map(funding => ({
                    fid: funding.fid,
                    status: funding.status,
                    currency: funding.currency,
                    amount: funding.amount,
                    method: funding.method,
                    created_at: funding.created_at,
                    details: funding.details
                  }))
                }, null, 2)
              }
            ]
          };
        } catch (error) {
          logToFile('ERROR', 'Error in list_fundings tool', error);
          
          if (error instanceof z.ZodError) {
            const errorMessage = error.errors.map(err => `${err.path.join('.')}: ${err.message}`).join(', ');
            return {
              content: [
                {
                  type: "text",
                  text: `Validation error: ${errorMessage}`
                }
              ]
            };
          }
          
          return {
            content: [
              {
                type: "text",
                text: `Error listing fundings: ${error instanceof Error ? error.message : String(error)}`
              }
            ]
          };
        }
      }
    );
  • Zod schema for validating input parameters to the list_fundings tool.
    const ListFundingsSchema = z.object({
      limit: z.number().int().positive().max(100).optional(),
      marker: z.string().optional(),
      method: z.string().optional(),
      status: z.string().optional(),
      fids: z.string().optional(),
    });
  • Registers the list_fundings tool on the MCP server with input schema and handler function reference.
    server.tool(
      "list_fundings",
      {
        description: "List fundings with optional filtering parameters",
        inputSchema: {
          type: "object",
          properties: {
            limit: {
              type: "number",
              description: "Number of objects to return (max 100, default 25)",
              minimum: 1,
              maximum: 100
            },
            marker: {
              type: "string",
              description: "Pagination marker"
            },
            method: {
              type: "string",
              description: "Filter by funding method"
            },
            status: {
              type: "string",
              description: "Filter by funding status"
            },
            fids: {
              type: "string",
              description: "Comma-separated funding IDs to filter by"
            }
          }
        }
      },
      async (params): Promise<ToolResult> => {
        try {
          const validatedParams = ListFundingsSchema.parse(params);
          logToFile('INFO', 'List fundings tool called', validatedParams);
          
          const response = await client.getFundings(validatedParams);
          
          if (!response.success || !response.payload || response.payload.length === 0) {
            return {
              content: [
                {
                  type: "text",
                  text: "No fundings found with the specified criteria."
                }
              ]
            };
          }
          
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify({
                  success: true,
                  count: response.payload.length,
                  fundings: response.payload.map(funding => ({
                    fid: funding.fid,
                    status: funding.status,
                    currency: funding.currency,
                    amount: funding.amount,
                    method: funding.method,
                    created_at: funding.created_at,
                    details: funding.details
                  }))
                }, null, 2)
              }
            ]
          };
        } catch (error) {
          logToFile('ERROR', 'Error in list_fundings tool', error);
          
          if (error instanceof z.ZodError) {
            const errorMessage = error.errors.map(err => `${err.path.join('.')}: ${err.message}`).join(', ');
            return {
              content: [
                {
                  type: "text",
                  text: `Validation error: ${errorMessage}`
                }
              ]
            };
          }
          
          return {
            content: [
              {
                type: "text",
                text: `Error listing fundings: ${error instanceof Error ? error.message : String(error)}`
              }
            ]
          };
        }
      }
    );
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/blaze-xyz/bitso-mcp'

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