Skip to main content
Glama
Sign In
@ktmcp/beezup

@ktmcp/beezup

by ktmcp-cli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

SetMerchantOrderInfoListV3

Send a batch of up to 100 operations to update merchant information for orders via the BeezUP Merchant API.

Instructions

Send a batch of operations to set 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": "SetMerchantOrderInfoListV3"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are present, so the description carries full responsibility. It confirms the tool modifies data (sets information) and imposes a batch limit, but it does not disclose side effects, idempotency, authentication requirements, or what happens on partial failures.

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, focused sentence with no wasted words. It is well front-loaded with the action and resource, though it could benefit from additional structure (e.g., separating key details).

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?

Given the tool's complexity as a batch operation with no output schema and sibling tools, the description is incomplete. It lacks information on input format, success/failure indicators, and relationship to other order modification tools.

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

Parameters3/5

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

The input schema has zero properties, and schema description coverage is 100%, so the baseline is 3. The description adds the batch limit hint but no further parameter details, which is acceptable given no parameters are defined.

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 clearly states the tool's action ('Send a batch of operations to set an Order's merchant information') and includes a useful constraint ('max 100 items per call'). It distinguishes from sibling tools like SetMerchantOrderInfo (singular) and other batch versions, though it could be more specific about what 'merchant information' entails.

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 on when to use this tool versus alternatives such as SetMerchantOrderInfo or ClearMerchantOrderInfoList. There is no mention of prerequisites, error conditions, or when not 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