Skip to main content
Glama
Sign In
@ktmcp/beezup

@ktmcp/beezup

by ktmcp-cli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ConfigureChannelCatalogProductValueOverrideCopy

Copies a product value override configuration from one product to another within a BeezUP channel catalog.

Instructions

Copy channel catalog product value override

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states 'copy' without explaining side effects, permissions required, or whether the operation is reversible. The agent cannot infer safety or idempotency from this alone.

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

Conciseness3/5

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

The description is extremely concise (one phrase), but at the cost of omitting crucial context. It does not earn its place as it fails to provide enough information to justify its brevity. A balance between conciseness and completeness is needed.

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 complexity of the domain with many sibling tools, the description is insufficient. It does not explain what a 'product value override copy' entails, what the tool outputs, or any dependencies. The agent is left guessing the operation's purpose and outcome.

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

Parameters4/5

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

There are zero parameters in the input schema. With no parameters to document, the description cannot add meaning beyond what the schema provides. Baseline score of 4 is appropriate as there is no deficiency to penalize.

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

Purpose3/5

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

The description 'Copy channel catalog product value override' specifies a verb+resource, but lacks specificity to distinguish from sibling tools like 'OverrideChannelCatalogProductValues' or 'GetChannelCatalogProductValueOverrideCopy'. The word 'copy' is ambiguous—does it create a new override or duplicate an existing one? Minimal clarity.

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 on when to use this tool versus alternatives such as 'DeleteChannelCatalogProductValueOverride' or 'ConfigureChannelCatalogProductValueOverrideCopy'. No prerequisites or exclusions mentioned, leaving the agent without context for appropriate invocation.

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