Skip to main content
Glama
haasonsaas

MCP Utility Tools

by haasonsaas

cache_clear

Clear all cached entries or specific namespaces to free memory and ensure data freshness in MCP workflows.

Instructions

Clear all entries from the cache or a specific namespace

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namespaceNoClear only this namespace, or all if not specified

Implementation Reference

  • Handler implementation for the cache_clear tool. Clears the entire cache using cache.clear() and returns the number of entries cleared before clearing.
    case "cache_clear": {
      const size = cache.size;
      cache.clear();
      
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            success: true,
            cleared_entries: size
          })
        }]
      };
    }
  • Enhanced handler for cache_clear tool supporting optional namespace clearing. Iterates and deletes keys with matching prefix if namespace provided, otherwise clears all. Returns count of cleared entries.
    case "cache_clear": {
      const { namespace } = args as any;
      
      if (namespace) {
        let cleared = 0;
        const prefix = `${namespace}:`;
        for (const key of cache.keys()) {
          if (key.startsWith(prefix)) {
            cache.delete(key);
            cleared++;
          }
        }
        
        return {
          content: [{
            type: "text",
            text: JSON.stringify({
              success: true,
              namespace,
              cleared_entries: cleared
            })
          }]
        };
      } else {
        const size = cache.size;
        cache.clear();
        
        return {
          content: [{
            type: "text",
            text: JSON.stringify({
              success: true,
              cleared_entries: size
            })
          }]
        };
      }
    }
  • src/index.ts:136-143 (registration)
    Tool registration in the tools list, including name, description, and empty input schema.
    {
      name: "cache_clear",
      description: "Clear all entries from the cache",
      inputSchema: {
        type: "object",
        properties: {}
      }
    },
  • Tool registration for v2 with support for namespace parameter in input schema.
    {
      name: "cache_clear",
      description: "Clear all entries from the cache or a specific namespace",
      inputSchema: {
        type: "object",
        properties: {
          namespace: {
            type: "string",
            description: "Clear only this namespace, or all if not specified"
          }
        }
      }
    },
  • Cache storage Map used by cache_clear and other cache tools. Defined identically in index-v2.ts.
    const cache = new Map<string, CacheEntry>();
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Clear' implies a destructive operation, the description doesn't specify whether this action is reversible, what permissions are required, whether it affects performance, or what happens to applications relying on cached data. For a destructive operation with zero annotation coverage, this represents a significant gap in behavioral transparency.

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 a single sentence that efficiently communicates the core functionality. Every word earns its place, and the structure is front-loaded with the primary action and scope clearly stated without unnecessary elaboration.

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 cache operation with no annotations and no output schema, the description is insufficient. It doesn't explain what 'clearing' entails operationally, whether it's synchronous or asynchronous, what confirmation (if any) is provided, or potential side effects. Given the complexity of cache operations and lack of structured metadata, the description should provide more complete contextual information.

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 description mentions 'a specific namespace' which aligns with the single 'namespace' parameter in the schema. With 100% schema description coverage, the schema already documents that this parameter clears only the specified namespace or all if not specified. The description adds minimal value beyond what the schema provides, meeting the baseline for 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 action ('Clear') and target ('all entries from the cache or a specific namespace'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like cache_delete, which might delete specific entries rather than clearing entire namespaces.

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?

The description provides no guidance on when to use this tool versus alternatives like cache_delete or batch_operation. It mentions the option to clear all entries or a specific namespace, but doesn't explain when one approach is preferable over the other or when other tools might be more appropriate.

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/haasonsaas/mcp-utility-tools'

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