Skip to main content
Glama
Sign In
@ktmcp/beezup

@ktmcp/beezup

by ktmcp-cli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ClearMerchantOrderInfoList

Clear merchant information from a batch of up to 100 orders in a single API call.

Instructions

[DEPRECATED] Send a batch of operations to clear an Order's merchant information (max 100 items per call)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Description mentions a batch size limit but lacks any detail on side effects, reversibility, authorization needs, or response behavior. The discrepancy between description and schema further undermines 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?

Short but incomplete and misleading. The '[DEPRECATED]' tag is useful, but the description omits critical information, making it not earn its place.

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 0 parameters and no output schema, the description is severely insufficient. It does not explain how to specify orders or what the request body should contain, making the tool unusable from this definition.

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?

Input schema has 0 properties while description suggests the tool accepts a batch of operations. The description fails to explain how to specify which orders to clear, leaving the agent unable to construct a valid request.

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?

Description claims 'Send a batch of operations to clear an Order's merchant information' but input schema has 0 properties, making the actual invocation mechanism unclear. The tool appears to require some input to specify which orders, but the schema contradicts this.

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

Usage Guidelines1/5

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

No guidance on when to use this deprecated tool versus alternatives like ClearMerchantOrderInfoListV3. The empty schema offers no help in understanding how to use it.

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