Skip to main content
Glama
NLACE-COM

mcp-supermercados-cl

by NLACE-COM

Armar la canasta más barata (repartida por cadena)

build_cheapest_basket

Compare prices across Chilean supermarkets and build the cheapest basket by selecting each item from its lowest-priced store. Shows total cost, single-store alternative, and savings.

Instructions

Toma una lista de ítems y, por CADA ítem, elige la cadena donde sale más barato (por precio por unidad cuando todas lo informan), agrupando la compra por cadena (la leche en una, el pan en otra). Devuelve plan por cadena, picks por ítem con alternativas, basketTotal (comprando cada cosa donde es más barata), singleStore y splitSaving (ahorro vs comprar todo en una sola cadena), y missing. Por defecto compara jumbo, santaisabel y unimarc (las que responden desde el servidor); tottus/lider requieren el puente de navegador (browserHtml de search_products). NO agrega al carro: para eso usa add_to_cart (hoy solo Jumbo, con sesión); para el resto quedan los links (url) de cada producto.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesÍtems en texto libre, ej. ["leche colun 1L", "pan de molde", "arroz 1kg"].
storesNoCadenas a comparar. Por defecto jumbo, santaisabel y unimarc (tottus/lider bloquean el fetch del servidor).
branchIdNoSucursal para precios locales de cadenas Cencosud, ej. "jumboclj512".
Behavior4/5

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

With no annotations, the description carries full burden. It describes the selection logic, return fields, default stores, and limitations. While it does not cover rate limits or authorization, the behavior is sufficiently transparent for a comparison tool.

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 a single dense paragraph that conveys all necessary information. It is front-loaded with the main action, but could benefit from slightly better structure. Every sentence is informative.

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 the tool's moderate complexity (3 parameters, no output schema), the description covers the purpose, return fields, default behavior, limitations, and sibling differentiation comprehensively.

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?

The description adds operational context beyond the schema, such as default store list and the requirement for tottus/lider to use browserHtml. With 100% schema coverage, the description provides useful semantic additions.

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 that the tool takes a list of items and selects the cheapest store per item, returning aggregated results. It distinguishes itself from siblings like add_to_cart by explicitly stating what it does not do (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 Guidelines5/5

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

The description provides explicit guidance on when to use this tool (to find the cheapest basket across stores) and when not to (use add_to_cart for adding items to cart). It also mentions that for tottus/lider, browserHtml from search_products is needed, implying prerequisite steps.

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