Skip to main content
Glama
ThiagoJacobLannes

kuantokusta-mcp

by ThiagoJacobLannes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
searchA

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).

get_productA

Get full details and all store prices for a KuantoKusta product.

Pass the product URL from a search result. Returns the product name, description, technical specs (45+ attributes), and all store offers sorted by total price (product + shipping) — so you always see the true cheapest option, not just the lowest sticker price.

Args: url: KuantoKusta product URL from a search result, e.g. "https://www.kuantokusta.pt/p/1967884/mini-com-congelador-smeg-fa120e"

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.6/5.0

Scored across 2 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: search finds products and get_product retrieves full details for a specific product URL, eliminating any ambiguity.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern: 'search' and 'get_product', making the naming predictable and clear.

Tool Count4/5

With only two tools, the server is minimal but covers the core workflow of searching and viewing product details. It is slightly under the typical range but reasonable for a focused price comparator.

Completeness4/5

The tool surface covers searching and retrieving product details, which are the primary actions. Minor gaps exist, such as no direct category browsing or comparison tools, but agents can work around these.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources