Skip to main content
Glama
cdek-shopping-mcp

cdek-shopping-mcp

by heahoh

search_products

Search the cdek.shopping catalog for products, brands, or categories, then refine results with facet filters, sorting, and pagination. Return only available filters when needed.

Instructions

Search products, brands and categories in the cdek.shopping catalog.

Args:
    q: Free-text search query, e.g. "Apple смартфон синий".
    filter: Facet filters as "key=value" strings (from a prior search response).
    sort: One of PRICE_ASC, PRICE_DESC, DEFAULT.
    page: Page number, 1-based.
    per_page: Results per page (max 100).
    only_filters: If true, return only the available filters, not results.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
qNo
pageNo
sortNo
filterNo
per_pageNo
only_filtersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose real behavior: 1-based pagination, a per_page ceiling of 100, the sort vocabulary, and a mode switch (only_filters) that suppresses results. It omits authentication/permission requirements, error behavior, and result shape, which matters for a zero-annotation tool.

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 purpose line is front-loaded and each parameter entry is one short line with no filler. The Args block is a dense enumeration rather than prose, which is functional but not elegant.

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?

All six parameters are explained, which is the main gap given 0% schema coverage. However, there is no output schema and the description never indicates what a result contains, whether facet data accompanies results, or how to detect the end of pagination — leaving real uncertainty for a search tool.

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?

Schema coverage is 0%, so the description must document all six parameters, and it does: query example, filter format ('key=value' strings sourced from a prior response), sort enum values, page numbering base, page size cap, and the flag's effect. The only gap is that 'key' values themselves are not described or exemplified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Search products, brands and categories in the cdek.shopping catalog'), which is clear and concrete. It does not, however, distinguish itself from siblings such as search_autocomplete, list_category_products, or catalog_categories, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'filter ... (from a prior search response)' hints at a facet-refinement workflow, and only_filters implies a two-step discover-then-search pattern. There is no explicit guidance on when to prefer this over search_autocomplete or the category/collection listing tools.

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