Skip to main content
Glama
Sign In
HacknPlan MCP Server

HacknPlan MCP Server

by Lint111
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

clear_cache

Clear cached metadata and work items by specifying a cache key pattern to resolve data freshness issues.

Instructions

Clear cached data (metadata, work items, etc.). Use pattern to clear specific cache entries.

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
patternNoCache key pattern to clear (e.g., "/projects/123" clears all project 123 cache)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv7.2.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool clears cached data, which implies destructiveness, but does not specify what exactly is cleared, whether the action is reversible, or any side effects. This is insufficient for a destructive operation with no annotation safety net.

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?

The description is extremely concise with only two sentences, no redundant information. Every word earns its place, making it easy to parse quickly.

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

Completeness3/5

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

For a simple tool with one optional parameter and no output schema, the description is adequate but incomplete. It does not clarify what happens when no pattern is provided (e.g., clears all cache), which is a notable gap. The sibling 'clear_deletion_cache' suggests a related tool, but no differentiation is provided.

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 schema covers 100% of parameters with descriptions. The description adds 'use pattern to clear specific cache entries,' which restates the schema's purpose. It provides no new format or syntax details beyond the schema, so the added value is minimal, meeting the baseline.

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?

Description clearly states the action: clearing cached data, including examples like metadata and work items. It provides a clear verb-resource pairing. However, it does not explicitly distinguish from the sibling 'clear_deletion_cache', so not a perfect 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 description includes a usage hint ('Use pattern to clear specific cache entries'), which gives context on when to use the pattern parameter. However, it lacks guidance on when not to use the tool or alternatives, such as when to use clear_deletion_cache instead.

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