Skip to main content
Glama

Zoya.bg

search_products

Search public storefront pages; call session_start first for active contexts and permissions. Continue by passing opaque next_cursor as cursor, preserving query/context/filters/limit exactly. Empty products plus next_cursor means more candidates remain. Stop when cursor is null, quota challenges, user has enough results, or upstream asks to retry later. Never fabricate cursors or auto-export a catalog. Up to 24 parents/call, 5 public pages and 100 unique returned variants/chain; max10 results/call. search_window_limited=true remains: never claim exhaustive results or cheapest in the whole store. search_changed requires restarting without cursor. Prices accept numbers or decimal strings. No stock promise.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
cursorNo
currencyNoEUR
languageNobg
max_priceNo
min_priceNo
storefrontNozoya.bg
package_size_gNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so richly: per-call and per-chain caps (24 parents, 5 public pages, 100 variants, max 10 results), partial-coverage semantics (search_window_limited=true forbids claiming exhaustive or cheapest results), no stock guarantee, and a prohibition on fabricating cursors or auto-exporting a catalog.

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?

Purpose and prerequisite are front-loaded, then pagination contract, then stop conditions, then limits and caveats — a sensible order. The prose is telegraphic and dense, but nearly every clause carries a distinct operative constraint rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter tool with no annotations and no output schema, the description covers pagination, limits, and result-trust caveats well and mentions 'products' and 'variants' as the returned shape. However, roughly half the input parameters (storefront, currency, language, package_size_g, price bounds semantics) remain undefined anywhere, which an agent needs to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and it only partly does. It explains the opaque cursor contract (must be passed back as cursor with query/filters/limit preserved unchanged), the limit ceiling, and that prices accept numbers or decimal strings. It says nothing about storefront, currency, language, package_size_g, or the min/max price semantics beyond type.

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 first clause gives a specific verb and resource with scope: 'Search public storefront pages'. It also names the prerequisite sibling ('call session_start first for active contexts and permissions'), which separates it from stateful cart/context tools without needing their schemas.

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?

Strong continuation and termination guidance: stop when cursor is null, on quota challenges, when the user has enough results, or when upstream asks to retry. It also states the session_start prerequisite and the search_changed restart rule. It does not differentiate from sibling listing tools like list_new_products or list_bestsellers, which is the main gap.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources