Skip to main content
Glama
bizino

BOS MCP Server

by bizino

bos_cart_add_item

Adds a product to the cart using product ID and quantity. Supports optional variant ID and notes for customization.

Instructions

Add item to cart

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
product_idYes
quantityYes
variant_idNo
notesNo

Implementation Reference

  • Handler function for bos_cart_add_item – sends a POST request to /mcp/cart/items with the provided args (product_id, quantity, optional variant_id, notes).
      handler: async (args, client) => client.post('/mcp/cart/items', args),
    },
  • Input schema for bos_cart_add_item defining required fields (product_id: string, quantity: number) and optional fields (variant_id: string, notes: string).
    schema: {
      product_id: { type: 'string' },
      quantity: { type: 'number' },
      variant_id: { type: 'string', optional: true },
      notes: { type: 'string', optional: true },
    },
  • Tool definition/registration as part of the cartTools array in src/tools/bos.ts, exported and later registered via server.tool() in src/index.ts (line 58-75).
    {
      name: 'bos_cart_add_item',
      description: 'Add item to cart',
      schema: {
        product_id: { type: 'string' },
        quantity: { type: 'number' },
        variant_id: { type: 'string', optional: true },
        notes: { type: 'string', optional: true },
      },
      handler: async (args, client) => client.post('/mcp/cart/items', args),
    },
  • The client.post() method invoked by the handler – delegates to request() which performs the actual HTTP POST with retries and rate limiting.
      async post<T>(path: string, data?: any): Promise<T> {
        return this.request<T>('POST', path, data);
      }
    
      async put<T>(path: string, data?: any): Promise<T> {
        return this.request<T>('PUT', path, data);
      }
    
      async delete<T>(path: string): Promise<T> {
        return this.request<T>('DELETE', path);
      }
    }
Behavior2/5

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

No annotations exist, and the description does not disclose behavioral traits such as whether the cart is created if absent, what constraints exist (e.g., stock limits), or error conditions.

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?

At 4 words, the description is extremely short but not effectively concise—it omits necessary details. Front-loading is minimal but the content is insufficient for a tool with 4 parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool complexity (4 parameters, no output schema, no annotations, and many siblings), the description is severely incomplete. It fails to cover parameter usage, behavior, or output expectations.

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 its 4 parameters, and the description adds no meaning beyond the parameter names. Critical information about product_id, quantity, variant_id, and notes is missing.

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 'Add item to cart' clearly states the verb and resource (add item to cart), but does not differentiate from sibling tools like bos_cart_remove_item or bos_cart_update_item, which share similar contexts.

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 on when to use this tool (e.g., when a cart exists) or when to use alternatives. The description lacks context on prerequisites or exclusions.

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