Skip to main content
Glama
NLACE-COM

mcp-supermercados-cl

by NLACE-COM

Buscar productos

search_products

Search for products across Chilean supermarkets, compare prices including unit prices, and filter by store, price range, stock, and branch for real-time local availability.

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).
browserHtmlNoLíder y Tottus: HTML de la página de búsqueda (o el JSON de __NEXT_DATA__) obtenido en un navegador real que ya pasó el antibot. Si se entrega, se parsea eso en vez de hacer el fetch (que la cadena bloquea por fingerprint del cliente). Flujo: llamar sin browserHtml → se devuelve openUrl+browserSnippet → ejecutarlo en el navegador → reintentar con browserHtml.
inStockOnlyNotrue = solo productos con stock real.
Behavior4/5

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

Despite no annotations, the description explains key behaviors: price fields (price, listPrice, unitPrice), currency (CLP), local vs national scope with branchId, store-specific IP requirements, and the browserHtml flow. It does not mention rate limits or caching, but covers most critical aspects.

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?

The description is dense but well-organized, starting with purpose, then output fields, filters, sorting, and special notes. It is concise given the wealth of information, though slightly longer than ideal.

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?

With no output schema, the description enumerates output fields and explains price behavior. It mentions pagination parameters but does not detail total results or next-page handling. It references a sibling tool and store-specific quirks, providing sufficient context for a search tool.

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%, but the description adds significant extra meaning: it explains the output fields, price semantics, sorting logic (price: cheapest first, unitPrice: best per unit), filter effects, and the browserHtml retry mechanism. This goes well beyond the schema descriptions.

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 it searches products in a Chilean supermarket catalog and returns enriched results. It distinguishes from the sibling tool `get_product` for specific product price, providing a clear boundary.

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

Usage Guidelines5/5

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

Explicitly tells when to use this tool for broad search and when to use `get_product` for a single product's price. Also notes store-specific requirements (e.g., residential IP for some chains) and provides a workflow for handling antibot with `browserHtml`.

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