Skip to main content
Glama
haasonsaas

MCP Utility Tools

by haasonsaas

cache_delete

Remove specific data from cache storage to free up memory or update information. Specify a key to delete cached items.

Instructions

Delete a key from the cache

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesCache key to delete
namespaceNoOptional namespacedefault

Implementation Reference

  • Handler implementation for the cache_delete tool. Extracts key and optional namespace from arguments, constructs the full cache key using getCacheKey helper, deletes the entry from the cache Map if it exists, and returns a JSON response indicating success and whether the key existed.
    case "cache_delete": {
      const { key, namespace = "default" } = args as any;
      const cacheKey = getCacheKey(key, namespace);
      
      const existed = cache.delete(cacheKey);
      
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            success: true,
            key,
            namespace,
            existed
          })
        }]
      };
    }
  • Input schema definition for the cache_delete tool, specifying the required 'key' parameter and optional 'namespace'.
    {
      name: "cache_delete",
      description: "Delete a key from the cache",
      inputSchema: {
        type: "object",
        properties: {
          key: {
            type: "string",
            description: "Cache key to delete"
          },
          namespace: {
            type: "string",
            description: "Optional namespace",
            default: "default"
          }
        },
        required: ["key"]
      }
    },
  • Handler implementation for the cache_delete tool in the v1 index. Deletes the specified key from the cache and returns success status with existence info. No namespace support.
    case "cache_delete": {
      const { key } = args as { key: string };
      
      const existed = cache.delete(key);
      
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            success: true,
            key,
            existed
          })
        }]
      };
    }
  • Input schema for cache_delete in v1, requiring only the 'key' parameter (no namespace).
    {
      name: "cache_delete",
      description: "Delete a key from the cache",
      inputSchema: {
        type: "object",
        properties: {
          key: {
            type: "string",
            description: "Cache key to delete"
          }
        },
        required: ["key"]
      }
  • Helper function used by cache tools (including cache_delete) to generate namespaced cache keys.
    function getCacheKey(key: string, namespace: string = "default"): string {
      return `${namespace}:${key}`;
    }
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 'Delete' implies a destructive mutation, it doesn't specify whether deletion is permanent, reversible, or has side effects. It also omits information about permissions needed, error handling (e.g., if key doesn't exist), or performance characteristics like rate limits.

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, direct sentence with zero wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse at a glance.

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 mutation tool with no annotations and no output schema, the description is insufficient. It lacks critical context about what happens post-deletion (e.g., success/failure responses), error scenarios, or how it interacts with sibling tools like cache_clear. The high schema coverage doesn't compensate for these behavioral gaps.

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%, with both parameters ('key' and 'namespace') clearly documented in the schema. The description adds no additional parameter semantics beyond what's already in the structured schema, so it meets the baseline of 3 without compensating for gaps.

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 ('Delete') and resource ('a key from the cache'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like cache_clear (which might delete all keys) or cache_get/put, but the verb+resource combination is specific enough for basic understanding.

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_clear (for bulk deletion) or other cache operations. There's no mention of prerequisites, error conditions, or typical use cases, leaving the agent with minimal contextual direction.

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