Skip to main content
Glama
Sign In
Carrefour Drive MCP

Carrefour Drive MCP

by maximeallanic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

add_item_to_cart

Add or update a product in your Carrefour cart by EAN and quantity, selecting the store/drive service and sub-basket type. Returns updated cart totals.

Instructions

Adds or updates a product item in the authenticated user's cart on Carrefour France. Allows specifying the product EAN, desired quantity, the basket service (store/drive), and the sub-basket type (e.g. drive click-and-collect). Also accepts a tracking context to indicate the page type and ID from which the action was triggered. Returns updated cart totals and summary. (requires an authenticated Carrefour session)

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": {
      "ean": "<ean>",
      "counter": "<counter>",
      "basketServiceId": "<basketServiceId>",
      "subBasketType": "<subBasketType>"
    },
    "name": "add_item_to_cart"
  }
}

Input Schema

NameRequiredDescriptionDefault
eanYesThe EAN (barcode) of the product to add or update in the cart.
pageIdNoThe page identifier used for tracking (e.g. 'moncompte', 'search', 'productdetail', 'basket').
counterYesThe desired quantity of the product to set in the cart.
pageTypeNoThe type of page from which the add-to-cart action is triggered, used for tracking (e.g. 'moncompte', 'search', 'productdetail', 'basket').
subBasketTypeYesThe sub-basket type, e.g. 'drive_clcv' for drive click-and-collect.
basketServiceIdYesThe basket service ID identifying the store or drive service to use for the cart.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral transparency burden. It discloses the mutation semantics ('adds or updates'), the authentication requirement, and the return value ('updated cart totals and summary'). It does not discuss failure behavior or explicitly state that the quantity replaces rather than increments an existing item, but the essential side effects are covered.

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?

The description is front-loaded with the main verb and resource, and each sentence adds a distinct piece of information: action, parameters, tracking, return value, and auth requirement. It is slightly verbose and could be tightened, but it is not redundant.

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?

The description covers the action, auth requirement, and return information, which is important given no output schema. However, it does not address the sibling `add_item_to_cart_by_ean`, error/unauthenticated behavior, or clarify whether `counter` sets or increments quantity, leaving some ambiguity for a mutation 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 the schema already documents each parameter. The description adds grouping and context, such as 'basket service (store/drive)', 'sub-basket type (e.g. drive click-and-collect)', and 'tracking context', but it does not significantly expand beyond the schema definitions.

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 opening sentence names a specific action ('Adds or updates') and resource ('product item in the authenticated user's cart on Carrefour France'), and the description adds EAN, quantity, basket service, and sub-basket type. However, it does not distinguish this tool from the sibling `add_item_to_cart_by_ean`, so it stops short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides clear usage context: this is for adding or updating cart items under an authenticated Carrefour session, with optional tracking context. It does not provide explicit when-not-to-use guidance or name an alternative such as `add_item_to_cart_by_ean`, so it earns 4 rather than 5.

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

Deploy Server

Other Tools