Skip to main content
Glama
Sign In
@ktmcp/beezup

@ktmcp/beezup

by ktmcp-cli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

OverrideChannelCatalogProductValues

Override product values in a channel catalog to update specific fields, resolving data inconsistencies or applying targeted changes.

Instructions

Override channel catalog product values

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

Input Schema

NameRequiredDescriptionDefault
bodyNoRequest body

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

The description provides no behavioral traits beyond the verb 'Override'. With no annotations, it should disclose if this is a destructive write, whether it replaces or merges, permissions required, or side effects. It fails to do so.

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 (5 words). While it avoids verbosity, it sacrifices necessary detail. It is front-loaded but incomplete.

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 (nested object parameter, no output schema, many siblings), the description is insufficient. It lacks details on body structure, expected outcome, and when to use, making it inadequate for correct agent invocation.

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 coverage is 100% but the only parameter 'body' is described as 'Request body' with no properties defined. The description adds no meaning about what fields the body should contain, leaving the agent without essential guidance for invocation.

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 'Override channel catalog product values' specifies a clear verb ('Override') and resource ('channel catalog product values'), distinguishing it from siblings like DeleteChannelCatalogProductValueOverride. However, it could be more precise about what 'override' entails (e.g., replace all values or specific ones).

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 ConfigureChannelCatalogProductValueOverrideCopy or DeleteChannelCatalogProductValueOverride. The agent has no context for selection.

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