Skip to main content
Glama
bizino

BOS MCP Server

by bizino

bos_product_list

Retrieve a paginated list of products filtered by category, search query, or status.

Instructions

List products with pagination and filters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
page_sizeNo
category_idNo
searchNo
statusNo

Implementation Reference

  • The handler for 'bos_product_list' tool. It receives optional args (page, page_size, category_id, search, status) and delegates to client.get('/mcp/products', args), making a GET request to the BOS API.
    {
      name: 'bos_product_list',
      description: 'List products with pagination and filters',
      schema: {
        page: { type: 'number', optional: true },
        page_size: { type: 'number', optional: true },
        category_id: { type: 'string', optional: true },
        search: { type: 'string', optional: true },
        status: { type: 'string', enum: ['active', 'inactive'], optional: true },
      },
      handler: async (args, client) => client.get('/mcp/products', args),
    },
  • Input schema for 'bos_product_list': page (number, optional), page_size (number, optional), category_id (string, optional), search (string, optional), status (string enum active/inactive, optional).
    schema: {
      page: { type: 'number', optional: true },
      page_size: { type: 'number', optional: true },
      category_id: { type: 'string', optional: true },
      search: { type: 'string', optional: true },
      status: { type: 'string', enum: ['active', 'inactive'], optional: true },
    },
  • src/index.ts:54-76 (registration)
    Registration: the tool is registered via McpServer.tool() in the main entry point. The productTools array is spread into allTools, then each tool is iterated and registered with its zodSchema and handler.
    // 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,
            };
          }
        }
      );
    }
  • The BosApiClient.get() method which is called by the handler. It delegates to request('GET', ...) and sends query params for list requests.
    // BUG 2+3 FIX: GET now accepts optional query params
    async get<T>(path: string, params?: Record<string, any>): Promise<T> {
      return this.request<T>('GET', path, undefined, params);
    }
Behavior2/5

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

No annotations are provided, and the description only states it lists products with pagination/filters. It does not disclose behavioral traits such as whether it returns full product details, authentication requirements, rate limits, or ordering behavior. For a listing tool, this is insufficient.

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 very concise (7 words) but lacks structure. It is front-loaded with the action, but there is no additional information. While concise, it sacrifices completeness for brevity.

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 5 parameters, no output schema, and no annotations, the description is insufficient. It does not explain the response format, default pagination values, or how filters interact. The tool's context is incomplete for effective agent use.

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?

The input schema has 0% parameter descriptions, and the description only vaguely mentions 'pagination and filters'. It does not explain the meaning of each parameter (e.g., page, page_size, category_id, search, status) beyond their names and types. The description fails to compensate for the lack of schema coverage.

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 it lists products with pagination and filters. It distinguishes from sibling tools like bos_product_search (search-focused) or bos_product_count (count). However, it doesn't explicitly differentiate from bos_product_categories or bos_product_list siblings.

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 usage guidelines provided. The description does not mention when to use this tool versus alternatives like bos_product_search or bos_product_categories. There is no context for optimal use cases.

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