Skip to main content
Glama
Sign In
Openworker E-Commerce MCP Server

Openworker E-Commerce MCP Server

by tukimtk-design
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ecommerce_get_pending_orders

Query unfulfilled orders on Shopee, TikTok Shop, or Lazada by specifying the platform, enabling you to view and process pending transactions.

Instructions

Query unfulfilled orders

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": {
      "platform": "<platform>"
    },
    "name": "ecommerce_get_pending_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full transparency burden. It only says 'Query unfulfilled orders,' which weakly implies a read operation, but it does not disclose what 'unfulfilled' covers, whether platform is required, what the response looks like, or any side effects.

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 short, front-loaded, and free of filler words. However, it is so minimal that it borders on under-specification, preventing a top score.

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

Completeness2/5

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

For a tool with no annotations, no output schema, and an undocumented required parameter, the description is not complete enough. It should at least mention the platform requirement and the nature of the returned orders, but it does neither.

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

Parameters1/5

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

The sole parameter 'platform' has 0% schema description coverage, and the description does not mention it at all. The description fails to compensate for the missing parameter documentation, leaving the acceptable values and purpose of 'platform' entirely unspecified.

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 ('Query') and a clear resource ('unfulfilled orders'), making the tool's basic purpose obvious. It does not explicitly differentiate it from sibling tools such as ecommerce_get_store_metrics or ecommerce_fulfill_order, so it stops short of a 5.

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

Usage Guidelines2/5

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

No guidance is given about when to use this tool versus alternatives like ecommerce_fulfill_order or ecommerce_get_store_metrics. The intended use case is only loosely implied by the name and description, with no explicit exclusions or alternative routing.

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

Deploy Server

Other Tools