Skip to main content
Glama
ThiagoJacobLannes

kuantokusta-mcp

search

Search for products on KuantoKusta.pt with filters for price, brand, and category. Use dynamic filters from the response to refine results by product-specific attributes.

Instructions

Search for products on KuantoKusta.pt — Portugal's main price comparator.

Returns up to 48 products per page plus available_filters showing all filter options that can be applied to narrow the results. Filters are dynamic and change per product type — always read available_filters from the response rather than guessing values.

Recommended workflow:

  1. Call search with just query (and optionally sort/price range).

  2. Read available_filters in the response to see areas, brands, and product-specific filters (color, capacity, energy class, typology…).

  3. Call search again with the desired filter values to get refined results.

Args: query: Search keywords, e.g. "frigorífico", "iphone 15", "tv 55 polegadas". area: Top-level category — use a value from available_filters where field="area". Example: "Electrodomésticos", "Informática". family: Sub-category within an area — use a value from available_filters where field="family". Example: "Grandes Electrodomésticos". sort: "cheap" (default) | "expensive" | "popular" | "alphabetical" | "newest". price_min: Minimum price in EUR (integer). price_max: Maximum price in EUR (integer). brands: List of brand names — use values from available_filters where field="brand". Example: ["Samsung", "LG"]. features: Dict of product-type-specific filter values — keys and valid values come from available_filters where field is NOT area/family/brand. Example: {"tipologia_s": "combinados", "cor_s": "inox", "classe_energetica_s": "classe a"}. For a laptop search the keys would be different (ram_s, os_s, etc.) — always derive them from the previous call's available_filters. page: Results page number (default 1; ~48 products per page).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
areaNo
pageNo
sortNocheap
queryYes
brandsNo
familyNo
featuresNo
price_maxNo
price_minNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Discloses pagination up to 48 products, dynamic filters, and iterative refinement. Although no annotations exist, it adequately describes read-only behavior without explicit mention of non-destructiveness.

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?

Well-structured with sections and bullet-pointed args. Slightly lengthy but every sentence adds value; front-loaded purpose.

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?

Covers all necessary aspects: workflow, parameter usage, dynamic filters, and output schema existence. Suitable for complex multi-parameter 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 lacks parameter descriptions (0% coverage), but the tool description compensates with thorough explanations, examples, and derivation rules for each parameter, adding significant meaning.

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 for products on KuantoKusta.pt, a price comparator. It distinguishes from sibling get_product by focusing on multi-product search with filters and pagination.

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 a recommended 3-step workflow using available_filters dynamically. However, it doesn't explicitly contrast with the sibling tool or state when not to use this tool.

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/ThiagoJacobLannes/kuantokusta-mcp'

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