Skip to main content
Glama
bquigley1

Finix MCP Server

by bquigley1

create_buyer

Create a new buyer identity in Finix by providing email, first name, last name, and phone number to establish payment processing profiles.

Instructions

This tool creates a new Buyer Identity in Finix.

It takes the following arguments:

  • email (str): The email address of the buyer.

  • first_name (str): The first name.

  • last_name (str): The last name.

  • phone (str): The phone number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesThe email address of the buyer
first_nameYesThe first name
last_nameYesThe last name
phoneYesThe phone number

Implementation Reference

  • The main handler function that implements the create_buyer tool. It validates credentials, constructs the buyer payload, posts to Finix /identities endpoint, and returns the new identity ID.
    const createBuyer = async (client: FinixClient, _context: FinixContext, params: any): Promise<any> => {
      try {
        if (!client.hasCredentials()) {
          throw new Error('Finix username and password are required for this operation. Please configure FINIX_USERNAME and FINIX_PASSWORD in your environment.');
        }
    
        const { email, first_name, last_name, phone } = params;
        
        const payload = {
          entity: {
            email,
            first_name,
            last_name,
            phone
          },
          type: 'PERSONAL',
          identity_roles: ['BUYER']
        };
    
        const response = await client.post('/identities', payload);
        
        if (response.error) {
          throw new Error(`Error creating buyer: ${response.error.message}`);
        }
        
        // Return just the ID like Stripe MCP
        return { id: response.data.id };
    
      } catch (error) {
        throw error;
      }
    };
  • Zod schema defining the input parameters for the create_buyer tool: email, first_name, last_name, phone.
    const createBuyerParameters = () => z.object({
      email: z.string().email().describe('The email address of the buyer'),
      first_name: z.string().describe('The first name'),
      last_name: z.string().describe('The last name'),
      phone: z.string().describe('The phone number')
    });
  • Tool factory registration defining the 'create_buyer' method, its description, parameters, annotations, and linking to the execute handler.
    const tool: ToolFactory = () => ({
      method: 'create_buyer',
      name: 'Create Buyer',
      description: createBuyerPrompt(),
      parameters: createBuyerParameters(),
      annotations: createBuyerAnnotations(),
      actions: {
        identities: {
          create: true
        }
      },
      execute: createBuyer
    });
  • Central registry where the createBuyer tool is included in the allTools array for export.
    export const allTools: ToolFactory[] = [
      // Search & Documentation
      searchDocs,
      
      // Identities (Buyers/Sellers)
      createBuyer,
      createSeller,
      listBuyers,
      listSellers,
      
      // Payment Links
      createPaymentLink,
    ];
Behavior2/5

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

With no annotations provided, the description carries full burden but provides minimal behavioral information. It states this is a creation operation but doesn't disclose important traits: whether this requires authentication, what happens on duplicate emails, what the response contains, whether there are rate limits, or what happens after creation. 'Creates' implies mutation but lacks details about permissions, side effects, or error conditions.

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

Conciseness4/5

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

Appropriately sized with two sentences: purpose statement followed by parameter listing. The structure is front-loaded with the core purpose first. However, the parameter listing is somewhat redundant given identical schema descriptions, and the description could be more efficient by focusing on value-added information.

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

Completeness2/5

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

For a creation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what a 'Buyer Identity' is in the Finix context, what happens after creation, what the tool returns, or any error conditions. With 4 required parameters and mutation behavior, more context about the operation's implications and results is needed for proper agent usage.

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 all parameters with identical descriptions. The description lists parameters but adds no additional meaning beyond what's in the schema - no format requirements, validation rules, or examples. With complete schema coverage, baseline is 3 even without extra param info in description.

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 'creates a new Buyer Identity in Finix' - a specific verb ('creates') with resource ('Buyer Identity') and system context ('Finix'). It distinguishes from siblings like 'create_seller' (different resource) and 'list_buyers' (different operation). However, it doesn't explicitly differentiate from 'create_payment_link' which creates a different resource type.

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?

No guidance on when to use this tool versus alternatives. The description doesn't mention when to create a buyer versus other operations like listing buyers or creating sellers. It provides no context about prerequisites, typical workflows, or scenarios where this tool is appropriate versus other tools in the sibling list.

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/bquigley1/finix-mcp'

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