Skip to main content
Glama
bquigley1

Finix MCP Server

by bquigley1

list_sellers

Retrieve seller information from Finix payment processing services. Filter results by email or limit the number of records returned for efficient data management.

Instructions

This tool will fetch a list of Sellers from Finix.

It takes two arguments:

  • limit (int, optional): The number of sellers to return.

  • email (str, optional): A case-sensitive filter on the list based on the seller's email field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
emailNo

Implementation Reference

  • The main handler function that implements the list_sellers tool. It queries the Finix identities endpoint with optional limit and email filters, filters the results for sellers (identity_roles includes 'SELLER'), and returns an array of seller IDs.
    const listSellers = 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 { limit, email } = params;
        
        // Build query parameters  
        const queryParams = new URLSearchParams();
        
        if (limit) queryParams.append('limit', limit.toString());
        if (email) queryParams.append('email', email);
    
        const response = await client.get(`/identities?${queryParams.toString()}`);
        
        if (response.error) {
          throw new Error(`Error listing sellers: ${response.error.message}`);
        }
        
        const data = response.data;
        const identities = data._embedded?.identities || [];
        
        // Filter for sellers only and return just IDs like Stripe
        const sellers = identities
          .filter((identity: any) => identity.identity_roles?.includes('SELLER'))
          .map((seller: any) => ({ id: seller.id }));
        
        return sellers;
    
      } catch (error) {
        throw error;
      }
    };
  • Zod schema defining the input parameters for the list_sellers tool: optional limit (1-100) and email filter.
    const listSellersParameters = () => z.object({
      limit: z.number().int().min(1).max(100).optional().describe(
        'A limit on the number of objects to be returned. Limit can range between 1 and 100.'
      ),
      email: z.string().optional().describe(
        'A case-sensitive filter on the list based on the seller\'s email field. The value must be a string.'
      )
    });
  • Tool factory registration defining the 'list_sellers' method, its name, description, parameters, annotations, permissions, and linking to the execute handler. Exported for use in the tools index.
    const tool: ToolFactory = () => ({
      method: 'list_sellers',
      name: 'List Sellers',
      description: listSellersPrompt(),
      parameters: listSellersParameters(),
      annotations: listSellersAnnotations(),
      actions: {
        identities: {
          read: true
        }
      },
      execute: listSellers
    });
    
    export default tool;
  • Prompt providing the natural language description of the list_sellers tool, used in the tool's description field.
    const listSellersPrompt = () => `
    This tool will fetch a list of Sellers from Finix.
    
    It takes two arguments:
    - limit (int, optional): The number of sellers to return.
    - email (str, optional): A case-sensitive filter on the list based on the seller's email field.
    `;
  • Annotations providing metadata hints for the list_sellers tool such as idempotent, read-only, etc.
    const listSellersAnnotations = () => ({
      destructiveHint: false,
      idempotentHint: true,
      openWorldHint: true,
      readOnlyHint: true,
      title: 'List sellers'
    });
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 mentions 'fetch a list' which implies a read-only operation, but doesn't specify whether this requires authentication, has rate limits, pagination behavior, error conditions, or what format the returned list takes. For a tool with zero annotation coverage, this leaves significant behavioral aspects undocumented, though it at least correctly indicates it's a retrieval operation rather than a mutation.

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 perfectly concise and well-structured. It opens with the core purpose, then clearly lists parameters with brief explanations. Every sentence serves a purpose with zero redundancy. The two-sentence structure is front-loaded with the main function followed by parameter details - an efficient pattern that wastes no words while covering essential information.

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 2 parameters with 0% schema coverage and no output schema, the description provides adequate but minimal coverage. It explains what the tool does and what parameters mean, but lacks information about return format, error handling, authentication requirements, and usage context relative to sibling tools. For a simple list operation, this might be sufficient, but the absence of output details and behavioral context leaves gaps that could hinder effective tool selection and invocation.

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?

With 0% schema description coverage, the description compensates well by explaining both parameters: 'limit' as 'The number of sellers to return' and 'email' as 'A case-sensitive filter on the list based on the seller's email field.' This adds meaningful context beyond the bare schema, clarifying the purpose and usage of each optional parameter. The description doesn't provide format examples or edge cases, but gives sufficient semantic understanding for basic use.

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 tool's purpose: 'fetch a list of Sellers from Finix' - a specific verb ('fetch') and resource ('Sellers from Finix'). It distinguishes from siblings like 'create_seller' (creation vs. listing) and 'list_buyers' (different resource type), though it doesn't explicitly contrast with 'search_finix_docs' which serves a different function. The purpose is unambiguous but could be slightly more specific about what 'Sellers' represent in this context.

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 when to prefer 'list_sellers' over 'search_finix_docs' for seller-related queries, or how it differs from 'list_buyers' in terms of use cases. There's no discussion of prerequisites, context, or typical scenarios where this tool would be appropriate versus other listing or search operations available in the sibling tools.

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