alza-mcp

Overview Schema Source Related Servers Discussions Admin

Search Alza products

search_products

Read-onlyIdempotent

Search Alza.cz's catalog by keyword to get available products with price, stock, and rating. Filter by price, category, or stock to compare options and start research.

Instructions

Search the Alza.cz catalog by keyword. Use this for product discovery — finding what's available, comparing options, or starting research. Returns a list with product code, name, price, stock (from the card's purchase CTA), and rating. To get full details for one product, follow up with get_product. Sorting: Alza's search page ignores server-side sort, so price-asc / price-desc / rating scan up to ~72 top-ranked candidates (3 pages) and sort them client-side — candidatesScanned reports how many were scanned; for an absolute price floor also pass max_price. in_stock: true keeps only products with a live purchase CTA. Read-only.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	1-indexed result page (follows Alza's rendered pagination). Only pages Alza actually renders are reachable — a page beyond the rendered set returns no results rather than repeating page 1. Paginating this way does not change which page the sweep scans (sorting still scans from page 1).
`sort`	No	Sort order, default 'relevance'. Alza's search page ignores server-side sort parameters, so price (asc/desc) and rating sorts gather candidates from up to 3 result pages (~72 items — the top of Alza's relevance ranking) and sort them client-side; the response's `candidatesScanned` says how many candidates were scanned. 'newest' is best-effort (Alza's newest-sort is client-side JS, so it returns relevance order). For an absolute price floor, also pass `max_price` and/or narrow `category_id`.
`limit`	No	Maximum number of results to return. Default 20, max 50.
`query`	Yes	Search keywords. Required. Example: 'iPhone 15 Pro', 'PlayStation 5', 'gaming mouse Logitech'.
`in_stock`	No	If true, keep only products purchasable right now (card shows a 'Do košíku'/'Vybrat variantu' purchase CTA; cards with a 'Hlídat' watch button are excluded). Derived from the search card's CTA — for real delivery dates use `get_product`.
`max_price`	No	Maximum price in the locale's currency.
`min_price`	No	Minimum price in the locale's currency.
`category_id`	No	Restrict the search to a specific category id. Use list_categories to discover ids.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`page`	Yes
`query`	Yes
`total`	Yes
`pageSize`	Yes
`products`	Yes
`candidatesScanned`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Sep 15, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Despite annotations already declaring readOnlyHint, openWorldHint, and idempotentHint, the description adds rich behavioral context: it explains Alza's server-side sort being ignored, the client-side scanning of ~72 candidates, the `candidatesScanned` field, and the nuances of `in_stock` and `newest` sort. No contradiction with annotations.

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 detailed but well-structured: it starts with the core purpose, then adds return info, then caveats about sorting and filtering. Every sentence earns its place, though it is slightly longer than needed and could be tightened without losing value.

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 output schema and 100% schema coverage, the description is complete: it names the returned fields (code, name, price, stock, rating), warns about pagination behavior, and covers edge cases like `newest` being best-effort. Nothing critical is missing for correct invocation.

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?

Parameter schema coverage is 100%, but the description goes far beyond the schema. It explains the practical effect of `sort` (client-side sorting, candidatesScanned), clarifies `in_stock` is derived from the purchase CTA, and notes `max_price` as an absolute floor. This adds substantial meaning beyond the raw type/description in the schema.

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 'Search the Alza.cz catalog by keyword' and defines its purpose as product discovery, comparing options, or starting research. It distinguishes itself from the sibling `get_product` by explicitly saying to follow up with that tool for full details, making it unambiguous.

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?

It explicitly says 'Use this for product discovery' and instructs to follow up with `get_product` for full details. It also notes when-passing `max_price` for an absolute price floor, effectively guiding usage based on user intent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.