Cachly — AI Cognitive Brain

cache_delete

Delete one or more cache keys from a specific instance to remove stale entries. Returns count of keys actually deleted.

Instructions

Permanently delete one or more keys from a running cache instance (uses Redis DEL). This operation is destructive and irreversible — deleted keys cannot be recovered. Deleting a non-existent key is safe and returns 0 for that key (no error). Returns the count of keys that were actually deleted (existing keys only). Use this to explicitly remove stale entries; prefer cache_set with a short TTL for auto-expiring data. Do NOT use this to clear an entire instance — use the dashboard or delete_instance for that.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "instance_id": "<instance_id>",
      "keys": "<keys>"
    },
    "name": "cache_delete"
  }
}

Input Schema

Name	Required	Description	Default
`keys`	Yes	One or more cache keys to delete. Accepts exact keys only (no glob patterns — use cache_keys to list first).
`instance_id`	Yes	UUID of the cache instance to delete keys from (get from list_instances)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.9.12May 6, 2026

addedInput schema / properties / instance_id / description

Added value: +"UUID of the cache instance to delete keys from (get from list_instances)"

changedInput schema / properties / keys / description

Previous value: -"One or more cache keys to delete"New value: +"One or more cache keys to delete. Accepts exact keys only (no glob patterns — use cache_keys to list first)."

First observedv0.2.0Apr 21, 2026

TDQS

A5/5.0

Behavior5/5

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

Declares destructive and irreversible nature, safe handling of non-existent keys, and return value (count of deleted keys). No annotations provided, but description fully covers behavioral traits.

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?

Concise, front-loaded with delete action, then explains implications and usage. Every sentence is informative without excess.

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

Completeness5/5

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

No output schema needed since return value is described. Description covers all necessary context for using this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds context beyond schema: instance_id should come from list_instances, keys must be exact (no glob) and recommends cache_keys to list. Schema coverage is 100% so baseline is 3, but description adds significant value.

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?

Clearly states it permanently deletes keys from a running cache instance, distinguishing it from siblings like cache_set, cache_keys, and delete_instance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use (remove stale entries), when not to use (prefer cache_set with short TTL, don't clear entire instance), and names alternatives (cache_set, delete_instance, dashboard).

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

Deploy Server