Skip to main content
Glama
cdek-shopping-mcp

cdek-shopping-mcp

by heahoh

recommendations

Fetches related and personalized product suggestions for storefront placements, scoped by product, category, region, and optional user history.

Instructions

Get personalized/related product recommendations for given placements.

Args:
    placements: Required list of placement codes identifying where the
        recommendations will be shown (e.g. "product_page", "cart").
    product_id: Product IDs to base "related to this" recommendations on.
    category_id: Category ID to scope recommendations to.
    region_id: Region/location ID affecting availability and pricing.
    page: Page number, 1-based.
    per_page: Results per page.
    user_history: Opaque user-history token used to personalize results.

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": {
      "placements": "<placements>"
    },
    "name": "recommendations"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
per_pageNo
region_idNo
placementsYes
product_idNo
category_idNo
user_historyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose useful behavior beyond the schema: region_id affects availability and pricing, user_history is an opaque personalization token, and page is 1-based. It omits result shape, ordering logic, whether personalization degrades without user_history, and any rate/auth constraints.

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?

Purpose is front-loaded in a single sentence, followed by a compact Args block where each line adds parameter meaning without filler. No redundant restatement of the tool name.

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 seven-parameter read tool with no annotations and no output schema, the definition covers intent and parameters well but says nothing about what comes back, default page size, or how results behave when personalization inputs are absent. Adequate to invoke, not fully complete.

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 description coverage is 0%, yet the docstring documents all seven parameters with meaning the bare schema titles cannot convey: placement codes with concrete examples, 'related to this' semantics for product_id, pricing/availability effects of region_id, 1-based paging, and the opaque nature of user_history. Only minor gaps remain, such as the expected format of placement codes beyond the two examples.

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 and resource: 'Get personalized/related product recommendations for given placements', and the placements concept distinguishes it from pure search/list siblings. It never names an alternative tool explicitly, so differentiation comes from the resource scope rather than routing language.

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 implied by the placements argument and the 'related to this' phrasing for product_id, which tells an agent this is a merchandising/recommendation call rather than a catalog lookup. There is no explicit when-to-use versus catalog_categories, list_category_products, or search_products, and no guidance on when to omit optional params.

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