Skip to main content
Glama
cdek-shopping-mcp

cdek-shopping-mcp

by heahoh

get_product_summary

Retrieve a compact product summary card by product ID for quick display or embedding in listings and interfaces.

Instructions

Get a short summary card for a product (for compact display/embedding).

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": {
      "product_id": "<product_id>"
    },
    "name": "get_product_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It indicates the return is a 'short summary card' but does not specify what fields are included, whether the operation is read-only, what permissions are needed, or how errors are handled, leaving significant behavioral gaps for a retrieval 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 description is a single concise sentence with the main purpose front-loaded and a useful parenthetical qualifier. It avoids unnecessary wording, though it could pair the display intent with one sentence of selection guidance.

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 simple one-parameter read tool with no output schema, the description gives a general sense of the return as a short summary card. It remains incomplete because it does not clarify what the summary contains or how it differs from get_product, which matters for an agent choosing among catalog tools.

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

Parameters2/5

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

There is one required parameter, product_id, but schema description coverage is 0%, so the schema supplies no semantic detail. The description does not explain the parameter's expected format, source, or behavior when the ID is invalid or missing, so it fails to compensate for the coverage gap.

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?

The description uses a specific verb and resource: 'Get a short summary card for a product.' The parenthetical 'for compact display/embedding' distinguishes it from a full product lookup, though it does not explicitly name or compare with sibling tools such as get_product.

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 'for compact display/embedding,' which suggests when a lightweight summary is preferable to a full product record. However, there is no explicit when-to-use guidance, no exclusion conditions, and no named alternative such as get_product.

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