Skip to main content
Glama
Sign In
@ktmcp/beezup

@ktmcp/beezup

by ktmcp-cli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ClearChannelCatalogExportationCache

Clears the cached exportation data for channel catalogs, ensuring subsequent exports reflect the latest changes.

Instructions

Clear the exportation cache

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

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 must fully disclose behavior. It only says 'clear', implying mutation, but does not state whether the cache is cleared for all channels, whether the action is reversible, or if it impacts other operations. This is inadequate for a destructive operation.

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, concise sentence that is front-loaded. It avoids wordiness but may be too brief, lacking crucial context. Still, it is well-structured for a zero-parameter tool.

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 zero parameters, no output schema, and no annotations, the description should explain what the 'exportation cache' is and the implications of clearing it. It fails to provide this context, leaving the agent with insufficient information to decide safely.

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 no parameters (100% coverage), so the description does not need to add parameter details. The baseline score of 3 is appropriate; the description adds no extra meaning beyond the name and schema.

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 name 'ClearChannelCatalogExportationCache' and description 'Clear the exportation cache' clearly indicate the tool clears a specific cache related to channel catalog exportation. It is distinct from its sibling 'GetChannelCatalogExportationCacheInfo'. However, it could be more explicit about what 'exportation cache' means and how it differs from other cache-related tools.

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, nor are there any prerequisites or context mentioned (e.g., effect on ongoing exports, need to call after changes). The description lacks any usage recommendations.

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