Skip to main content
Glama
cdek-shopping-mcp

cdek-shopping-mcp

by heahoh

list_orders

Retrieve the authenticated user's CDEK shopping orders; set CDEK_SHOPPING_TOKEN to a valid bearer token to avoid an authentication error.

Instructions

List the authenticated user's orders.

Requires the CDEK_SHOPPING_TOKEN environment variable to be set to a
valid bearer token; otherwise this returns an authentication error.

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": "list_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

With no annotations, the description carries the full behavioral burden. It does disclose one valuable trait beyond structured data: the required bearer token and the failure mode (an authentication error). It says nothing about pagination, result ordering, result limits, or what an order record contains, which are significant gaps for a list tool with no output schema.

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?

Two short sentences, front-loaded with the action and scope, followed by the precondition. Nothing is padded or redundant, though the line-wrapped formatting of the second sentence is slightly awkward.

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 zero-parameter read tool with no output schema and no annotations, the definition covers the main practical obstacle to a successful call (auth token) and states the failure behavior. It would be stronger with a sentence on whether the result is paginated or bounded, but it is close to complete for this complexity level.

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 tool takes zero parameters, so there is nothing for the description to clarify; the baseline for a parameterless tool applies. The auth note is environment configuration rather than a parameter, so it neither adds nor detracts here.

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 gives a specific verb and resource plus an ownership scope: 'List the authenticated user's orders.' That is unambiguous and clearly distinct from the catalog-oriented siblings (list_category_products, search_products, etc.), though it never explicitly contrasts itself with them.

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 by the resource name; there is no explicit statement of when to reach for this tool, and no alternatives are named. The one piece of real guidance is the precondition that CDEK_SHOPPING_TOKEN must be set, which is a prerequisite rather than a when-to-use rule.

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