Skip to main content
Glama
bizino

BOS MCP Server

by bizino

bos_customer_address_list

Retrieve all addresses associated with a customer by providing their unique ID.

Instructions

List all addresses for a customer

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idYes

Implementation Reference

  • Tool 'bos_customer_address_list' is defined as an entry in the customerTools array. It has a schema requiring customer_id and its handler delegates to client.get('/mcp/customers/${args.customer_id}/addresses').
    {
      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`),
    },
  • Handler function: async (args, client) => client.get('/mcp/customers/${args.customer_id}/addresses') — makes a GET request to list addresses for the given customer_id.
    handler: async (args, client) => client.get(`/mcp/customers/${args.customer_id}/addresses`),
  • Input schema: { customer_id: { type: 'string' } } — requires a single required string parameter customer_id.
    schema: { customer_id: { type: 'string' } },
  • src/tools/index.ts:4-9 (registration)
    McpTool interface definition: name, description, schema, and handler shape used by all tool definitions.
    export interface McpTool {
      name: string;
      description: string;
      schema: Record<string, any>;
      handler: (args: any, client: BosApiClient) => Promise<any>;
    }
  • src/stdio.ts:54-74 (registration)
    Tool registration loop: iterates over all tool arrays (including customerTools), converts schema via toZodSchema, and registers with the McpServer.
    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, and the description does not disclose any behavioral traits such as pagination, sorting, or whether it returns full address details. The description is too brief to be transparent.

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?

The description is extremely concise (5 words), which is acceptable for a simple tool but lacks detail. It is front-loaded but too minimal.

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 tool's simplicity (one parameter, no output schema), the description is incomplete; it does not mention what the response contains or any default behavior.

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?

The input schema has 0% description coverage for the parameter 'customer_id', and the tool description does not add any meaning beyond the parameter 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?

The description 'List all addresses for a customer' clearly states the action (list) and resource (addresses for a customer), and distinguishes it from sibling tools like create, update, delete.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use vs alternatives, but the purpose is clear from the name and sibling tools; it's the obvious choice for listing addresses.

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