Mercadona MCP Server

Set quantity

set_quantity

Set the exact quantity of a product in your cart. Use 0 to remove the item. Returns the updated cart.

Instructions

Set the exact quantity of a product in the cart. Quantity 0 removes it. Returns the updated cart.

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": {
      "product_id": "<product_id>",
      "quantity": "<quantity>"
    },
    "name": "set_quantity"
  }
}

Input Schema

Name	Required	Description	Default
`quantity`	Yes	Exact quantity (0 removes)
`product_id`	Yes	Product id

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 28, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and discloses that quantity 0 removes the product and that it returns the updated cart. However, it does not mention behaviors such as error handling if product is not in cart, idempotency, or authorization requirements.

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?

Two sentences, front-loaded with the primary action, no extra words. Every sentence adds value.

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 tool is simple with two parameters and 100% schema coverage, the description is nearly complete. It explains the return value and removal behavior. However, it lacks detail on what happens when product_id is not in the cart (e.g., does it add it or error?), which could be clarified.

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%, so baseline is 3. The description adds no new parameter information beyond what the schema already provides (e.g., 'Exact quantity (0 removes)'). The return value mention is not parameter-related.

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 verb 'set' and the resource 'exact quantity of a product in the cart', and distinguishes from siblings like add_to_cart and remove_from_cart by specifying exact quantity control including removal via zero.

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

Usage Guidelines3/5

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

The description implies usage for setting quantities precisely but does not explicitly state when to use this tool over siblings like add_to_cart or remove_from_cart. No when-not-to-use or alternative guidance is provided.

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

Deploy Server