remove_from_cart
Remove a product from your Intermarché Drive cart using its product ID.
Instructions
Retire complètement un produit du panier.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| product_id | Yes | Identifiant produit |
Remove a product from your Intermarché Drive cart using its product ID.
Retire complètement un produit du panier.
| Name | Required | Description | Default |
|---|---|---|---|
| product_id | Yes | Identifiant produit |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate destructiveHint=true and idempotentHint=true, which the description confirms with 'completely remove'. However, the description does not add new behavioral details beyond what annotations already provide, such as behavior when product is not in the cart.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence with no wasted words. It is appropriately concise for this simple tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simplicity of the tool (one parameter, no output schema, clear annotations), the description is minimally adequate but lacks information about error states or prerequisites. It could benefit from mentioning that the product must currently be in the cart.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already covers the single parameter 'product_id' with a description ('Identifiant produit'), achieving 100% coverage. The tool description adds no additional meaning or usage context for the parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action 'Retire complètement' (completely remove) and the resource 'un produit du panier' (a product from the cart). It effectively distinguishes from sibling tools like add_to_cart and update_quantity by indicating complete removal rather than adding or modifying quantity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, nor does it specify prerequisites or conditions. It simply states the action without context for decision-making.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/nicolasestrem/mcp-intermarche-drive'
If you have feedback or need assistance with the MCP directory API, please join our Discord server