Skip to main content
Glama
bcb-mcp
by msperlin

Clear Cache

clear_cache
Destructive

Delete cached parquet files for selected series or wipe the entire cache, including series data, query files, catalog searches, and metadata.

Instructions

Delete cached parquet files, either for selected series or everything.

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

Input Schema

NameRequiredDescriptionDefault
series_idsNoSeries to evict (ids or aliases). Omit to wipe the whole cache (parquet series, query files, catalog searches and metadata).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds the scope of destruction ('or everything'), but that same detail is already in the schema's series_ids description, and it says nothing about irreversibility or the cost of re-populating the cache.

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

Conciseness5/5

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

A single short sentence with the action front-loaded and the scope qualifier immediately after. No redundant or filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter tool with an output schema and destructive annotations, the definition covers purpose and both modes, so nothing essential is missing. A brief note on the consequence of an unscoped wipe would make it fully complete.

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?

Schema description coverage is 100%, so the single parameter is fully documented in structured form, establishing the baseline of 3. The description's 'selected series or everything' restates the schema rather than adding format or semantic detail beyond it.

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 gives a specific verb and resource ('Delete cached parquet files') plus the two scopes ('selected series or everything'), so the agent knows exactly what the tool does. It does not name or contrast with siblings such as cache_status or query_cache, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'either...or' phrasing implies the two usage modes (targeted eviction vs full wipe), which is minimal but real guidance. There is no explicit statement of when to prefer this over cache_status or query_cache, and no caution about choosing the full wipe.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.