Skip to main content
Glama
igorsafonov-gif

Mercadona MCP Server

Search products

search_products

Search for grocery products in your delivery area to get their IDs, names, and prices needed to add items to your cart.

Instructions

Find a product and its id (needed before add_to_cart), scoped to the user's delivery area. Use a short term; prefer the house brand 'Hacendado' unless asked otherwise. Returns matches with ids and prices.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 24)
queryYesSearch text, e.g. 'leche semidesnatada' or 'olive oil'
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses scoping to delivery area and output (matches with ids and prices). Does not mention pagination or errors, but is adequate for a search tool.

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, no wasted words, purpose front-loaded. Highly concise and efficient.

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 no output schema and no annotations, the description fully covers what the tool does, returns, and how to use it, including reference to sibling tool add_to_cart.

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

Parameters5/5

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

Schema coverage is 100%; description adds value beyond schema by advising on query length and brand preference, and contextualizing the output for add_to_cart.

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?

Clearly states 'Find a product and its id (needed before add_to_cart)' with specific verb and resource, and distinguishes from sibling tools like get_product and add_to_cart.

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?

Provides explicit advice: 'Use a short term; prefer the house brand Hacendado unless asked otherwise.' Implies when to use (before add_to_cart) but lacks explicit when-not or alternative tools.

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/igorsafonov-gif/mercadona-claude-extension'

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