Skip to main content
Glama
bizino

BOS MCP Server

by bizino

bos_product_search

Locate products in the BOS ERP system using name, SKU, or barcode search. Returns product details.

Instructions

Search products by name, SKU, or bar code

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query

Implementation Reference

  • The handler function for 'bos_product_search' tool - makes a GET request to '/mcp/products/search' with the query params.
    handler: async (args, client) => client.get('/mcp/products/search', args),
  • Input schema for 'bos_product_search' - expects a single 'q' (string) field as the search query.
    schema: { q: { type: 'string', description: 'Search query' } },
  • src/tools/bos.ts:27-27 (registration)
    Registration of the tool with name 'bos_product_search' and description 'Search products by name, SKU, or bar code' in the productTools array.
    name: 'bos_product_search',
  • src/index.ts:33-33 (registration)
    The productTools array (containing bos_product_search) is spread into allTools and then registered via server.tool() in the loop at lines 55-76.
    ...productTools,
  • The toZodSchema helper converts the tool's schema definition into a Zod schema for MCP SDK validation.
    export function toZodSchema(schema: Record<string, any>): z.ZodObject<any> {
      const shape: Record<string, z.ZodTypeAny> = {};
    
      for (const [key, def] of Object.entries(schema)) {
        let field: z.ZodTypeAny;
    
        switch (def.type) {
          case 'number':
            field = z.number();
            break;
          case 'boolean':
            field = z.boolean();
            break;
          case 'array':
            field = z.array(z.any());
            break;
          case 'object':
            field = z.record(z.any());
            break;
          case 'string':
          default:
            if (def.enum) {
              field = z.enum(def.enum);
            } else {
              field = z.string();
            }
            break;
        }
    
        if (def.description) {
          field = field.describe(def.description);
        }
    
        if (def.optional) {
          field = field.optional();
        }
    
        shape[key] = field;
      }
    
      return z.object(shape);
Behavior2/5

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

Description provides no details on search behavior (partial match, case sensitivity, pagination, sorting) and no annotations are present, leaving the agent uninformed about critical operational traits.

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?

Single sentence with no extraneous information, front-loaded with the core purpose.

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?

Minimally adequate for a simple search tool, but lacks return format, pagination, or error handling details, which are important for completeness.

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?

Although the input schema covers the parameter 'q' with 100% coverage, the description adds semantic value by specifying that the query can target name, SKU, or bar code, guiding the agent on acceptable input formats.

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?

Clearly states the tool searches products by specific attributes (name, SKU, bar code), differentiating it from sibling tools like bos_product_list (listing without search) and bos_product_show (single product by ID).

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?

Implies use when searching for products by name, SKU, or barcode, but does not explicitly state when to use this tool versus alternatives like bos_product_list or bos_product_show, nor when not to use it.

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