Skip to main content
Glama

Remove cart line

cart_remove_item
Destructive

Remove a cart line item.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "storeId": "<storeId>",
      "lineItemId": "<lineItemId>"
    },
    "name": "cart_remove_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeIdYesOkam store id.
lineItemIdYesLine item id from cart_get.

Output Schema

NameRequiredDescriptionDefault
cartNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / cart / properties / items / items / properties / product / properties / allergens / items / properties / code
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is covered structurally. The description adds nothing beyond that: no statement about irreversibility, what happens to cart totals or empty carts, or whether the call fails for an unknown line item. For a destructive operation it leaves the behavioral burden entirely to annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with zero filler, front-loaded with the action. It is terse to the point of under-specification, but nothing in it is wasteful.

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?

This is a destructive mutation, and the description omits essential context: whether removal is permanent, whether unknown line items error or no-op, and what follow-up calls (cart_get, cart_validate) are expected. An output schema and 100% parameter coverage exist, but the behavioral gap is large for a destructive tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both storeId and lineItemId are documented in the schema, including the useful hint that lineItemId comes from cart_get. The description adds no parameter meaning of its own, so the baseline 3 applies.

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?

"Remove a cart line item" gives a specific verb (remove) plus resource (cart line item), which cleanly separates it from cart_add_item and cart_update_item. It stops short of stating scope details such as whether the whole line is deleted versus a quantity decrement, so it is clear but not fully differentiated.

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 when-to-use or when-not-to-use guidance is given, and no sibling is named. An agent must infer that this is the right tool for deletion versus cart_update_item (likely quantity changes) purely from the tool name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources