Skip to main content
Glama
bizino

BOS MCP Server

by bizino

bos_customer_update

Update a customer's details such as name, phone, email, or address by providing their customer ID.

Instructions

Update customer information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idYes
nameNo
phoneNo
emailNo
addressNo

Implementation Reference

  • The handler function for bos_customer_update. It destructures customer_id from args, then calls client.put() to update the customer via PUT /mcp/customers/{customer_id}.
    handler: async (args, client) => {
      const { customer_id, ...data } = args;
      return client.put(`/mcp/customers/${customer_id}`, data);
    },
  • The input schema for bos_customer_update. Requires customer_id (string), with optional fields: name, phone, email, address.
    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 },
    },
  • src/index.ts:54-76 (registration)
    Registration loop in src/index.ts that iterates all tools (including bos_customer_update) and registers them with the MCP server using server.tool(). The tool's name, description, Zod schema, and handler are passed.
    // Register all tools with proper Zod schemas
    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,
            };
          }
        }
      );
    }
  • src/index.ts:36-46 (registration)
    The customerTools array (which contains bos_customer_update) is imported from ./tools/bos.js and spread into the allTools array.
      ...customerTools,
      ...inventoryTools,
      ...voucherTools,
      ...loyaltyTools,
      ...storeTools,
      ...checkoutTools,
      ...promotionTools,
      ...engagementTools,
      ...erpTools,
      ...smartTools,
    ];
Behavior2/5

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

No annotations are present, so the description carries the full burden. It does not disclose any behavioral traits such as side effects, permission requirements, whether updates are partial or full overwrites, or any rate limits. This is insufficient for a mutation tool.

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

Conciseness2/5

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

The description is a single three-word sentence. While short, it omits essential information, making it under-specified rather than concise. It fails to earn its place by leaving critical details unaddressed.

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?

Given the complexity of a customer update tool with five parameters, no output schema, and no annotations, the description is incomplete. It does not explain update behavior (e.g., partial vs full), return value, or error conditions, leaving the agent poorly informed.

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

Parameters2/5

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

With 0% schema description coverage, the description should compensate by explaining parameter meanings or constraints. It only says 'Update customer information,' adding no insight into fields like customer_id, name, phone, email, or address. The schema provides field names, but the description adds no value.

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 'Update customer information' clearly states the verb (update) and resource (customer information), making the purpose immediately understandable. However, it does not distinguish this tool from sibling tools like bos_customer_create or bos_customer_update (the name itself), so it lacks differentiation.

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 is provided regarding when to use this tool versus related tools (e.g., create, delete, show). There are no mentions of prerequisites, constraints, or recommended contexts.

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