Skip to main content
Glama
bizino

BOS MCP Server

by bizino

bos_customer_transactions

Retrieve payment transactions for a customer by providing their customer ID.

Instructions

Get payment transactions for a customer

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idYes

Implementation Reference

  • Handler for the bos_customer_transactions tool - makes a GET request to /mcp/customers/{customer_id}/transactions to retrieve payment transactions for a customer.
    {
      name: 'bos_customer_transactions',
      description: 'Get payment transactions for a customer',
      schema: { customer_id: { type: 'string' } },
      handler: async (args, client) => client.get(`/mcp/customers/${args.customer_id}/transactions`),
    },
  • Input schema for bos_customer_transactions - requires a single 'customer_id' string parameter.
      name: 'bos_customer_transactions',
      description: 'Get payment transactions for a customer',
      schema: { customer_id: { type: 'string' } },
      handler: async (args, client) => client.get(`/mcp/customers/${args.customer_id}/transactions`),
    },
  • Tool definition for bos_customer_transactions, part of the customerTools array in src/tools/bos.ts.
    {
      name: 'bos_customer_transactions',
      description: 'Get payment transactions for a customer',
      schema: { customer_id: { type: 'string' } },
      handler: async (args, client) => client.get(`/mcp/customers/${args.customer_id}/transactions`),
    },
  • The customerTools array (lines 270-392) that contains the bos_customer_transactions tool definition, exported and then spread into allTools in src/index.ts.
    export const customerTools: McpTool[] = [
      {
        name: 'bos_customer_list',
        description: 'List customers with pagination',
        schema: {
          page: { type: 'number', optional: true },
          page_size: { type: 'number', optional: true },
          search: { type: 'string', optional: true },
        },
        handler: async (args, client) => client.get('/mcp/customers', args),
      },
      {
        name: 'bos_customer_show',
        description: 'Get customer details by ID',
        schema: { customer_id: { type: 'string' } },
        handler: async (args, client) => client.get(`/mcp/customers/${args.customer_id}`),
      },
      {
        name: 'bos_customer_create',
        description: 'Create a new customer',
        schema: {
          name: { type: 'string' },
          phone: { type: 'string' },
          email: { type: 'string', optional: true },
          address: { type: 'string', optional: true },
        },
        handler: async (args, client) => client.post('/mcp/customers', args),
      },
      {
        name: 'bos_customer_update',
        description: 'Update customer information',
        schema: {
          customer_id: { type: 'string' },
          name: { type: 'string', optional: true },
          phone: { type: 'string', optional: true },
          email: { type: 'string', optional: true },
          address: { type: 'string', optional: true },
        },
        handler: async (args, client) => {
          const { customer_id, ...data } = args;
          return client.put(`/mcp/customers/${customer_id}`, data);
        },
      },
      {
        name: 'bos_customer_delete',
        description: 'Delete a customer',
        schema: { customer_id: { type: 'string' } },
        handler: async (args, client) => client.delete(`/mcp/customers/${args.customer_id}`),
      },
      {
        name: 'bos_customer_search',
        description: 'Search customers by name, phone or email',
        schema: { q: { type: 'string' } },
        handler: async (args, client) => client.get('/mcp/customers/search', args),
      },
      {
        name: 'bos_customer_orders',
        description: 'Get order history for a customer',
        schema: { customer_id: { type: 'string' } },
        handler: async (args, client) => client.get(`/mcp/customers/${args.customer_id}/orders`),
      },
      {
        name: 'bos_customer_transactions',
        description: 'Get payment transactions for a customer',
        schema: { customer_id: { type: 'string' } },
        handler: async (args, client) => client.get(`/mcp/customers/${args.customer_id}/transactions`),
      },
      {
        name: 'bos_customer_address_list',
        description: 'List all addresses for a customer',
        schema: { customer_id: { type: 'string' } },
        handler: async (args, client) => client.get(`/mcp/customers/${args.customer_id}/addresses`),
      },
      {
        name: 'bos_customer_address_create',
        description: 'Add a new address for a customer',
        schema: {
          customer_id: { type: 'string' },
          address_line_1: { type: 'string' },
          city: { type: 'string', optional: true },
          state: { type: 'string', optional: true },
          country: { type: 'string', optional: true },
          zip_code: { type: 'string', optional: true },
        },
        handler: async (args, client) => {
          const { customer_id, ...data } = args;
          return client.post(`/mcp/customers/${customer_id}/addresses`, data);
        },
      },
      {
        name: 'bos_customer_address_update',
        description: 'Update a customer address',
        schema: {
          customer_id: { type: 'string' },
          address_id: { type: 'string' },
          address_line_1: { type: 'string', optional: true },
          city: { type: 'string', optional: true },
          state: { type: 'string', optional: true },
        },
        handler: async (args, client) => {
          const { customer_id, address_id, ...data } = args;
          return client.put(`/mcp/customers/${customer_id}/addresses/${address_id}`, data);
        },
      },
      {
        name: 'bos_customer_address_delete',
        description: 'Delete a customer address',
        schema: { customer_id: { type: 'string' }, address_id: { type: 'string' } },
        handler: async (args, client) => client.delete(`/mcp/customers/${args.customer_id}/addresses/${args.address_id}`),
      },
      {
        name: 'bos_customer_loyalty_summary',
        description: 'Get loyalty points summary for a customer',
        schema: { customer_id: { type: 'string' } },
        handler: async (args, client) => client.get(`/mcp/customers/${args.customer_id}/loyalty`),
      },
      {
        name: 'bos_customer_count',
        description: 'Get total customer count with optional filters',
        schema: { status: { type: 'string', optional: true } },
        handler: async (args, client) => client.get('/mcp/customers/count', args),
      },
    ];
  • src/index.ts:55-76 (registration)
    Generic registration loop in src/index.ts that registers all tools (including bos_customer_transactions) with the MCP server.
    for (const tool of allTools) {
      const zodSchema = toZodSchema(tool.schema);
    
      server.tool(
        tool.name,
        tool.description,
        zodSchema.shape,
        async (args: any) => {
          try {
            const result = await tool.handler(args, client);
            return {
              content: [{ type: 'text' as const, text: JSON.stringify(result, null, 2) }],
            };
          } catch (error: any) {
            return {
              content: [{ type: 'text' as const, text: JSON.stringify({ error: error.message || 'Unknown error' }) }],
              isError: true,
            };
          }
        }
      );
    }
Behavior2/5

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

No annotations provided; description does not disclose behavioral traits like whether it's read-only, pagination, rate limits, or if it returns all transactions or just successful ones.

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

Conciseness3/5

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

Extremely concise (single short sentence) but at the cost of crucial information; no structuring aids like bullet points.

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?

With only one parameter and no output schema or annotations, the description fails to clarify what 'transactions' includes (e.g., all payment types, date range, order) or the return format.

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?

Input schema has 0% description coverage; the description does not explain what 'customer_id' represents or its format, leaving the parameter ambiguous beyond the name.

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

Purpose5/5

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

Description clearly states the verb 'Get' and the resource 'payment transactions for a customer', distinguishing it from sibling tools like bos_order_transactions and bos_customer_orders.

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 vs. alternatives such as bos_order_transactions or bos_customer_orders; lacks context about filtering or scope.

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/bizino/bos-mcp'

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