Skip to main content
Glama
Sign In
Carrefour Drive MCP

Carrefour Drive MCP

by maximeallanic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

carrefour_set_cookies

Store Carrefour.fr session cookies to enable account access for other tools. Accepts header string, JSON map, or array.

Instructions

Store your www.carrefour.fr session cookies so the other tools can act on your account. Accepts a raw cookie header ("a=1; b=2"), a JSON map, or a JSON array export (Playwright / EditThisCookie / DevTools). Get them from DevTools (F12) > Application > Cookies > https://www.carrefour.fr.

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": {
      "cookies": "<cookies>"
    },
    "name": "carrefour_set_cookies"
  }
}

Input Schema

NameRequiredDescriptionDefault
cookiesYesCookies as a header string, a JSON object, or a JSON array of cookie objects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states 'store' and implies a session-setting operation, but it doesn't disclose whether this overwrites existing cookies, whether it's persistent, or any side effects. The description is not misleading, but it lacks detail about behavioral nuances.

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 two sentences long, front-loaded with the purpose and formats, and the second sentence gives practical acquisition instructions. Every sentence serves a purpose with no fluff.

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?

Given a single parameter, no output schema, and no annotations, the description is complete. It explains what to pass, accepted formats, how to obtain the cookies, and why it's needed. No additional information seems necessary for usage.

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

Parameters4/5

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

The schema covers 100% with a clear description of the 'cookies' parameter. The tool description adds value by listing accepted formats (header string, JSON object, JSON array) and providing concrete examples ('a=1; b=2') and sources (Playwright, EditThisCookie, DevTools), enriching 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 what the tool does: 'Store your www.carrefour.fr session cookies' with a specific verb and resource. It explains the purpose ('so the other tools can act on your account') and distinguishes from sibling tools like carrefour_clear_session and carrefour_refresh_session by focusing on storing cookies.

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 gives clear context on when to use it (to enable other tools to act on your account) and provides practical guidance on obtaining cookies via DevTools. It doesn't explicitly mention when not to use it or alternatives like carrefour_browser_login, but the context is sufficient.

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