Skip to main content
Glama
maximeallanic

Carrefour Drive MCP

submit_checkout_payment

Submit the selected payment methods for a Carrefour checkout and retrieve updated totals, remaining balance, and available payment options to proceed with the drive order payment.

Instructions

Submits payment method selection for the authenticated user's checkout on Carrefour France. Sends the chosen payment methods (e.g. credit card by saved card ID, loyalty card with a specific amount) for a given basket service type (e.g. 'driveclcv' for drive click-and-collect). Returns the total and remaining amounts, available payment methods with provider tokens/URLs (Apple Pay, CB credit card, card pass, etc.), saved payment methods, and the payment group. Useful for initiating the payment step during checkout. (requires an authenticated Carrefour session)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paymentsYesList of payment method objects to apply. Each object can have: 'type' (e.g. 'CB' for credit card, 'CRF_LOYALTY_CARD' for Carrefour loyalty card), 'cardId' (for saved credit cards), and 'price' (object with 'value' in cents and 'scale' for fractional digits, used when partially paying with loyalty points). An empty array triggers retrieval of available payment methods.
apple_payNoWhether Apple Pay is available on the user's device. Sent as string 'true' or 'false' in the 'apple-pay' header.
google_payNoWhether Google Pay is available on the user's device. Sent as string 'true' or 'false' in the 'google-pay' header.
is_shortcutNoWhether this is a shortcut/express checkout flow. Usually false for standard checkout.
professionalNoProfessional account indicator. Usually null for standard consumers.
checkout_typeYesThe basket service type for the checkout (e.g. 'driveclcv' for drive click-and-collect). Sent as the 'checkout-type' request header.
device_fingerprint_idYesA device fingerprint ID used for fraud prevention, sent as the 'device-fingerprint-id' request header.
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the action (sends chosen payment methods), the return value (total/remaining amounts, available methods, saved methods, payment group), and the requirement of an authenticated session. It does not mention error handling or side effects, but the disclosed behavior is substantive.

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?

The description is three sentences with no fluff. It front-loads the main action, then describes inputs, outputs, and use case. Every sentence contributes value, making it concise yet complete.

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

Completeness4/5

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

Given the complexity (7 params, no output schema), the description covers the return values compensating for the missing output schema, notes the authentication prerequisite, and explains the overall purpose. It lacks explicit error behavior but is otherwise complete enough for an agent to invoke correctly.

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% with detailed descriptions for all 7 parameters, including examples like 'driveclcv' and nested payment object structure. The description reinforces examples but adds no significant new semantics beyond the schema, so the baseline score of 3 is appropriate.

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 uses a specific verb and resource: 'Submits payment method selection for the authenticated user's checkout.' It clearly distinguishes from sibling tools like validate_checkout_slot and validate_checkout_summary by focusing on the payment submission 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?

The description states it is 'Useful for initiating the payment step during checkout' and notes the prerequisite of 'an authenticated Carrefour session.' This provides clear context, though it does not explicitly mention alternatives or when not to use this tool compared to validation siblings.

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/maximeallanic/CarrefourDriveMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server