Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

zalando_suggest

Complete partial Zalando search queries with storefront-specific autocomplete suggestions; provide the partial keyword and required country market.

Instructions

Autocomplete a Zalando search query. Returns Zalando's own search-box query completions for a partial keyword, e.g. "running sho" -> "running shoes", "running shoes nike". market is required (there is no default storefront) and accepts 25 country storefronts — see zalando-markets for the full current list with domains.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesPartial search text to complete
marketYesZalando country storefront

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / market / enum
      Added value: +[
+  "at",
+  "be",
+  "ch",
+  "cz",
+  "de",
+  "dk",
+  "ee",
+  "es",
+  "fi",
+  "fr",
+  "gb",
+  "hr",
+  "hu",
+  "ie",
+  "it",
+  "lt",
+  "lu",
+  "lv",
+  "nl",
+  "no",
+  "pl",
+  "ro",
+  "se",
+  "si",
+  "sk"
+]
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

There are no annotations, so the description carries the burden. It discloses the core behavior (returning Zalando's own autocomplete completions for a partial keyword), the required market context, and illustrates the transformation with an example. It does not specify the exact response shape or failure behavior, but for a simple read-only autocomplete tool this is reasonably transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: it states the action immediately, gives a useful concrete example, and tucks the operational market caveat at the end. Every sentence earns its place and there is no redundant filler.

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?

For a two-parameter tool with fully documented schema fields, the description is nearly complete. It covers what the tool does, what inputs matter, that market is mandatory, and where to get the valid market list. The only real omission is the exact return structure, but the phrase 'returns query completions' plus the example is likely sufficient for an agent to invoke and interpret it.

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 schema already documents both parameters with 100% coverage, but the description adds meaningful context beyond it: market has no default and accepts 25 country storefronts, with a pointer to zalando-markets for the full list. It also clarifies q as a partial keyword through the example, reinforcing the schema's definition.

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 uses a specific verb and resource: 'Autocomplete a Zalando search query' and explains it returns 'Zalando's own search-box query completions for a partial keyword.' The concrete example ('running sho' -> 'running shoes') makes the behavior unmistakable and separates it from full-search tools.

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?

The description clearly frames the tool as the autocomplete/suggestion entry point and gives operationally relevant guidance: market is required, there is no default storefront, and users should consult zalando-markets for the canonical list. It does not explicitly state 'use zalando_search instead for full results,' but the context is clear enough that an agent would not confuse it with a search tool.

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

Deploy Server

Other Tools