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_local_sqlite_cache

Cache key-value data locally in SQLite to avoid repeated API requests and speed up e-commerce automation workflows.

Instructions

Local SQLite caching

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": {
      "action": "<action>",
      "key": "<key>"
    },
    "name": "ecommerce_local_sqlite_cache"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
valueNo
actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/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 of disclosing behavioral traits. It states only 'Local SQLite caching' and does not mention persistence semantics, side effects, cache expiration, concurrency behavior, or what happens on get versus set. This provides essentially no behavioral transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short, but this is under-specification rather than effective conciseness. It contains no useful information beyond the tool name, so it fails to earn its place as a meaningful description.

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

Completeness1/5

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

Given that there are no annotations, no output schema, and 0% schema description coverage, the description is far too incomplete. It omits the behavior of both actions, the key/value contract, return values, and any operational context within the ecommerce toolset. An agent cannot reliably select or invoke this tool based on the information provided.

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?

Schema description coverage is 0%, and the description does not compensate by explaining any parameters. It does not clarify that 'action' chooses between get and set, what 'key' represents, or how 'value' should be formatted. The absence of parameter semantics makes correct invocation largely guesswork.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Local SQLite caching' is a noun phrase that merely restates the tool name 'ecommerce_local_sqlite_cache' without a specific verb or resource action. It does not say what the tool does, such as retrieving or storing cached values, and it offers no differentiation from sibling tools.

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?

There is no guidance on when to use this tool versus alternatives or how it fits into the broader ecommerce workflow. The description does not mention use cases, prerequisites, or exclusions, leaving the agent to infer applicability from the schema alone.

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