Skip to main content
Glama
haasonsaas

MCP Utility Tools

by haasonsaas

cache_clear

Clear all cache entries or remove data from a specific namespace to free memory and reset cached results.

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 for cache_clear tool - clears all entries from the cache Map and returns the count of cleared entries.
    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 - supports optional namespace parameter to clear only entries in a specific namespace, or clears all if no namespace provided.
    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
            })
          }]
        };
      }
    }
  • Schema/definition for cache_clear tool in index.ts - no parameters required, clears entire cache.
    {
      name: "cache_clear",
      description: "Clear all entries from the cache",
      inputSchema: {
        type: "object",
        properties: {}
      }
    },
  • Schema/definition for cache_clear tool in index-v2.ts - supports optional namespace parameter to clear only a specific namespace.
    {
      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"
          }
        }
      }
    },
  • src/index.ts:188-191 (registration)
    Tool registration via ListToolsRequestSchema handler - cache_clear is registered as part of the tools array.
    // Register list handler
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
Behavior2/5

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

No annotations provided; description only states it clears entries, but does not disclose destructiveness, auth requirements, rate limits, or side effects. The burden is entirely on the description, which is insufficient.

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

Conciseness3/5

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

Single sentence is concise but front-loads the core action; however, it omits potentially useful details like return value or confirmation. Adequate but not exceptional.

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?

Given the simplicity (1 optional param, no output schema), the description is minimally complete. It covers the basic operation but lacks any additional context that would aid an agent in understanding implications.

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 coverage is 100%, and the description adds no extra meaning beyond the schema's own description. Baseline score of 3 applies as schema already explains the parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool clears cache entries, either all or a specific namespace, distinguishing it from siblings like cache_delete which likely targets individual entries.

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 when-to-use or when-not guidance; lacks mention of alternatives or prerequisites. Agent has no context on when cache_clear is appropriate versus cache_delete.

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