Skip to main content
Glama
Sign In
Carrefour Drive MCP

Carrefour Drive MCP

by maximeallanic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

validate_checkout_slot

Validates the checkout slot step for a given basket service type, submitting a device fingerprint to confirm slot selection and obtain payment links. Returns cart state, checkout step, and warnings to proceed.

Instructions

Validates the checkout slot step for a specific basket service type (e.g. 'driveclcv' for drive click-and-collect) on Carrefour France. Submits a device fingerprint ID and returns the current cart state, checkout step, store context, workflow steps, warnings, and available checkout links (payment, on-site payment, device fingerprint generator). Useful for confirming the slot selection step before proceeding to the payment step. (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": {
      "basket_service_type": "<basket_service_type>",
      "deviceFingerPrintId": "<deviceFingerPrintId>"
    },
    "name": "validate_checkout_slot"
  }
}

Input Schema

NameRequiredDescriptionDefault
basket_service_typeYesThe basket service type for checkout (e.g. 'driveclcv' for drive click-and-collect, 'lad' for home delivery, etc.)
deviceFingerPrintIdYesThe device fingerprint ID generated by the fingerprint generator service, used for fraud prevention during checkout.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description discloses the action (submits a device fingerprint ID) and enumerates the return contents (cart state, checkout step, store context, workflow steps, warnings, checkout links). It also states the authentication prerequisite. It does not explicitly state whether the operation has side effects, but 'validates' suggests read-only behavior.

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

Conciseness5/5

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

Three sentences, front-loaded with the action and resource, then return values and usage context. No redundancy; every sentence carries useful information.

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

Completeness5/5

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

Despite no output schema, the description lists the key return fields and positions the tool in the checkout flow (slot selection before payment). It also covers the required authentication, making it self-sufficient.

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 coverage is 100% and both parameters are fully described in the schema. The description adds an example for basket_service_type ('driveclcv') and mentions the device fingerprint context, but does not add significant meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool 'validates the checkout slot step' for a specific basket service type, naming Carrefour France and giving an example ('driveclcv'). It distinguishes from sibling tools like validate_checkout_summary by specifying the slot step rather than the summary step.

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 workflow context: 'Useful for confirming the slot selection step before proceeding to the payment step.' It also notes the authentication requirement, but does not explicitly name alternative tools or when not to use it.

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