Skip to main content
Glama
ibproduct

Memory Cache MCP Server

by ibproduct

clear_cache

Remove specific or all cached entries to free memory and ensure fresh data retrieval in the Memory Cache MCP Server.

Instructions

Clear specific or all cache entries

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoSpecific key to clear (optional - clears all if not provided)

Implementation Reference

  • Handler function for the 'clear_cache' tool. Parses arguments, calls CacheManager.delete(key) for specific key or CacheManager.clear() for all entries, and returns success/error text response.
    case 'clear_cache': {
      const { key } = request.params.arguments as { key?: string };
      if (key) {
        const success = this.cacheManager.delete(key);
        return {
          content: [
            {
              type: 'text',
              text: success
                ? `Successfully cleared cache entry: ${key}`
                : `No cache entry found for key: ${key}`,
            },
          ],
        };
      } else {
        this.cacheManager.clear();
        return {
          content: [
            {
              type: 'text',
              text: 'Successfully cleared all cache entries',
            },
          ],
        };
      }
    }
  • src/index.ts:135-147 (registration)
    Tool registration in ListToolsRequestSchema handler, including name, description, and input schema.
    {
      name: 'clear_cache',
      description: 'Clear specific or all cache entries',
      inputSchema: {
        type: 'object',
        properties: {
          key: {
            type: 'string',
            description: 'Specific key to clear (optional - clears all if not provided)',
          },
        },
      },
    },
  • Input schema definition for the clear_cache tool.
    inputSchema: {
      type: 'object',
      properties: {
        key: {
          type: 'string',
          description: 'Specific key to clear (optional - clears all if not provided)',
        },
      },
    },
  • CacheManager.clear() method: clears all cache entries and resets statistics.
    clear(): void {
      this.cache.clear();
      this.resetStats();
    }
  • CacheManager.delete(key) method: removes specific cache entry and updates stats, returns success boolean.
    delete(key: string): boolean {
      const entry = this.cache.get(key);
      if (entry) {
        this.stats.memoryUsage -= entry.size;
        this.cache.delete(key);
        this.stats.totalEntries = this.cache.size;
        return true;
      }
      return false;
    }
Behavior2/5

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

With no annotations, the description carries full burden but provides minimal behavioral insight. It implies a destructive action ('clear') but doesn't disclose permanence, side effects (e.g., performance impact), permissions required, or error handling. For a mutation tool, this leaves critical gaps in understanding its behavior.

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 a single, efficient sentence with zero waste. It's front-loaded with the core action and scope, making it easy to parse quickly. No extraneous details or repetition are present.

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?

For a destructive tool with no annotations and no output schema, the description is incomplete. It lacks information on permissions, side effects, return values, or error cases. Given the complexity of cache operations and the absence of structured safety hints, more context is needed for safe and effective use.

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 schema already documents the optional 'key' parameter. The description adds marginal value by implying the scope ('specific or all'), but doesn't explain key formats, validation, or default behavior beyond what's in the schema. Baseline 3 is appropriate given high schema coverage.

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 clearly states the verb ('clear') and resource ('cache entries'), specifying it can target 'specific or all' entries. It distinguishes from siblings like 'get_cache_stats' (read-only) and 'retrieve_data' (data access), but doesn't explicitly differentiate from 'store_data' (which might involve cache updates).

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 is provided. The description doesn't mention prerequisites (e.g., admin rights), typical scenarios (e.g., after data updates), or when to avoid it (e.g., during high traffic). It merely states what it does without contextual usage advice.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ibproduct/ib-mcp-cache-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server