Skip to main content
Glama
Sign In
@ktmcp/beezup

@ktmcp/beezup

by ktmcp-cli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Importation_SaveCustomColumn

Create or replace a custom column during importation to define custom data fields for BeezUP store management.

Instructions

Create or replace a custom column

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

Input Schema

NameRequiredDescriptionDefault
bodyNoRequest body

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 provided. The description only mentions 'create or replace', but does not disclose any behavioral traits such as authentication requirements, idempotency, or side effects (e.g., whether replace fully overwrites or merges).

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 one short sentence, which is concise and front-loaded. However, it could be slightly expanded to include more context without becoming verbose.

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 has a single nested object parameter, no output schema, and many sibling tools (especially Catalog_SaveCustomColumn), the description is insufficient. It does not explain the domain concept of custom columns or differentiate from similar tools.

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?

The input schema has one parameter 'body' with description 'Request body', which is generic. The description adds no additional meaning about the body structure or required fields, even though schema coverage is 100% but the schema itself is uninformative.

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 'Create or replace a custom column' clearly states the verb and resource. However, there is a sibling tool 'Catalog_SaveCustomColumn' with very similar purpose, and the description does not differentiate between them, which is a minor gap.

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 like 'Catalog_SaveCustomColumn'. No context on prerequisites or exclusions.

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