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

get_funding

Retrieve funding transaction data from the Bitso cryptocurrency exchange. This tool provides access to funding records with proper authentication and filtering capabilities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that validates input parameters, fetches the specific funding using the Bitso client, formats the response as text, and handles errors including validation errors.
        async (params): Promise<ToolResult> => {
          try {
            const validatedParams = GetFundingSchema.parse(params);
            logToFile('INFO', 'Get funding tool called', { fid: validatedParams.fid });
            
            const funding = await client.getFunding(validatedParams.fid);
            
            return {
              content: [
                {
                  type: "text",
                  text: `Funding Details:
    ID: ${funding.fid}
    Status: ${funding.status}
    Currency: ${funding.currency}
    Amount: ${funding.amount}
    Method: ${funding.method}
    Created: ${funding.created_at}
    Details: ${JSON.stringify(funding.details, null, 2)}`
                }
              ]
            };
          } catch (error) {
            logToFile('ERROR', 'Error in get_funding 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 retrieving funding: ${error instanceof Error ? error.message : String(error)}`
                }
              ]
            };
          }
        }
  • Zod schema used in the handler for input validation, requiring a 'fid' string.
    const GetFundingSchema = z.object({
      fid: z.string().min(1, "Funding ID is required"),
    });
  • MCP server tool registration for 'get_funding', providing tool name, description, input schema (mirroring Zod schema), and handler function.
    server.tool(
      "get_funding",
      {
        description: "Get details of a specific funding by ID",
        inputSchema: {
          type: "object",
          properties: {
            fid: {
              type: "string",
              description: "The funding ID to retrieve"
            }
          },
          required: ["fid"]
        }
      },
  • Supporting client method that performs the authenticated API call to Bitso's /fundings/{fid} endpoint, with caching, logging, and error handling.
    async getFunding(fid: string): Promise<Funding> {
      const cacheKey = this.getCacheKey(`/api/v3/fundings/${fid}`);
      const cached = this.getCachedData<Funding>(cacheKey);
      
      if (cached) {
        return cached;
      }
    
      try {
        const requestPath = `/api/v3/fundings/${fid}`;
        const authHeaders = this.createAuthHeaders('GET', requestPath);
        
        this.logToFile('INFO', 'Fetching funding from Bitso API...', { fid });
        
        const response: AxiosResponse<{ success: boolean; payload: Funding }> = await this.client.get(requestPath, {
          headers: authHeaders
        });
        
        if (!response.data.success) {
          throw new Error('API request failed');
        }
    
        const funding = response.data.payload;
        this.setCachedData(cacheKey, funding);
        
        this.logToFile('INFO', 'Funding fetched successfully', { fid });
        return funding;
      } catch (error) {
        this.logToFile('ERROR', 'Failed to fetch funding', { fid, error });
        throw 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