Skip to main content
Glama
NLACE-COM

mcp-supermercados-cl

by NLACE-COM

Buscar productos

search_products

Search products across Chilean supermarkets with real-time prices, stock filters, and unit price comparison. Filter by store, price range, and stock availability for optimal shopping.

Instructions

Busca productos en el catálogo de un supermercado chileno y devuelve resultados enriquecidos: name, brand, description, imageUrl, url. Precios en CLP: price es el precio vigente (con oferta si la hay), listPrice el normal cuando hay descuento, unitPrice/unit el precio por unidad base (kg/lt/un) para comparar formatos. Filtros opcionales: maxPrice/minPrice (CLP), inStockOnly; orden con sortBy (price = más barato primero, unitPrice = mejor precio por kg/lt). Con branchId (sucursal) los precios/stock son de esa tienda. Para el precio socio de un producto puntual, usar get_product.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPágina de resultados.
limitNoMáximo de resultados (1-50).
queryYesTexto de búsqueda, ej. "leche descremada" o "arroz grado 1".
storeNoCadena donde buscar: jumbo, santaisabel, unimarc, tottus o lider. unimarc/tottus/lider requieren IP residencial (la máquina del usuario).jumbo
sortByNoOrden: relevance (default), price (más barato primero) o unitPrice (mejor precio por kg/lt).relevance
branchIdNoCódigo de sucursal para precios/stock locales, ej. "jumboclj512". Omitir para catálogo nacional.
maxPriceNoFiltra productos con precio vigente <= a este valor (CLP).
minPriceNoFiltra productos con precio vigente >= a este valor (CLP).
inStockOnlyNotrue = solo productos con stock real.
Behavior4/5

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

Discloses price fields in CLP, branchId effect, sorting behavior, and store-specific IP constraints. No annotations, so description handles burden well. Missing pagination details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with main purpose and return fields; efficient paragraph. Could be slightly shorter but no wasted words.

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?

Covers main aspects of a search tool with 9 parameters; no output schema but return fields explained. Pagination behavior not detailed.

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?

Adds meaning beyond 100% schema coverage: explains unitPrice for comparison, price vs listPrice, branchId, and store enum caveats.

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 tool searches products in a Chilean supermarket catalog with enriched results, differentiating from get_product and other siblings.

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 context for when to use, mentions alternative get_product for specific product member price, and notes store IP requirements. Lacks explicit when-not-to-use but is clear overall.

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/NLACE-COM/mcp-supermercados-cl'

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