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_smart_diff_update

Compare current and target product states to identify changes, then apply only the differences to update listings across Shopee, TikTok Shop, and Lazada.

Instructions

Calculate deltas between states

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": {
      "currentState": "<currentState>",
      "targetState": "<targetState>"
    },
    "name": "ecommerce_smart_diff_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetStateYes
currentStateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries full responsibility for disclosing behavior, but it only says 'calculate deltas between states.' It doesn't disclose whether the tool mutates anything, what side effects exist, what output is returned, or whether it only reads/computes. The name's 'update' hints at mutation, but the description neither confirms nor denies it.

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 sentence with no filler and is easy to parse. It earns its place as a concise summary, though the brevity comes at the cost of missing substantial detail.

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 two required nested object parameters, no annotations, and no output schema, a one-sentence description is materially incomplete. An agent cannot infer the expected state shapes, the return value, potential side effects, or when this tool should be selected over the many ecommerce siblings.

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?

Schema description coverage is 0%, so the description needs to compensate, but it only vaguely references 'states' without explaining how currentState and targetState relate. It implies a comparison between the two but provides no format, semantics, or examples to help an agent construct valid inputs.

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 specifies a concrete action ('calculate') and a resource ('states'), giving a coherent purpose. However, it doesn't differentiate itself from sibling tools or explain what 'deltas' concretely means, and the 'update' in the name is not reflected in the description.

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 provided about when to use this tool versus alternatives. There are no use-case examples, no conditions, and no mention of related sibling tools like ecommerce_update_price_stock or ecommerce_batch_update_price_stock.

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