Skip to main content
Glama
bizino

BOS MCP Server

by bizino

bos_cart_remove_item

Remove a specific item from a cart using its unique item ID. The item is immediately deleted from the cart.

Instructions

Remove item from cart

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYes

Implementation Reference

  • The handler function that executes the 'Remove item from cart' logic. It sends a DELETE request to /mcp/cart/items/{item_id}.
    handler: async (args, client) => client.delete(`/mcp/cart/items/${args.item_id}`),
  • The input schema for the tool, requiring a single 'item_id' field of type string.
    schema: { item_id: { type: 'string' } },
  • The tool 'bos_cart_remove_item' is defined as an entry in the cartTools array within the Cart section (line 214). It has name, description, schema, and handler.
    {
      name: 'bos_cart_remove_item',
      description: 'Remove item from cart',
      schema: { item_id: { type: 'string' } },
      handler: async (args, client) => client.delete(`/mcp/cart/items/${args.item_id}`),
    },
  • The BosApiClient.delete method that actually performs the HTTP DELETE request to the API.
    async delete<T>(path: string): Promise<T> {
      return this.request<T>('DELETE', path);
    }
Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as idempotency, error handling (e.g., if item not in cart), or side effects. The description is insufficient for a safe operation.

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 (3 words), which is efficient but lacks necessary detail. It is front-loaded but 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 simple input (one string) and no output schema, the description should still explain the effect, such as item removal from cart and potential errors. The current description is too sparse for an agent to use reliably.

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?

Schema description coverage is 0%, and the description adds no additional meaning to the item_id parameter beyond its name. The agent has no information about expected format, constraints, or examples.

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 'Remove item from cart' clearly states the action and resource. However, it does not differentiate from sibling tools like bos_cart_clear or bos_cart_remove_voucher, which have similar removal semantics.

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 on when to use this tool versus alternatives such as bos_cart_clear or bos_cart_update_item. The agent receives no context on prerequisites, return behavior, or conditions.

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