Skip to main content
Glama

cachly — Explain it once. Every AI knows it.

forget_context

Delete one or more cached context entries. Use when context is stale or you want to force a fresh analysis. Supports glob patterns: "file:*" deletes all file summaries.

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": {
      "keys": "<keys>"
    },
    "name": "forget_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysYesKeys to delete (supports glob)
instance_idNoUUID of the cache instance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose meaningful behavior beyond the schema: glob matching and the implicit point that deleted context is regenerable ('force a fresh analysis'). It omits whether deletion is permanent, what happens when instance_id is omitted, and whether a count is returned.

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

Conciseness4/5

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

Three short sentences, front-loaded with the action, then the trigger, then the glob syntax. Nothing is padding. Minor deduction because the glob example could be folded into the trigger sentence for tighter scanning.

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?

The tool is simple (2 params, no nested objects, no output schema), so the definition is close to adequate. The remaining gaps matter for a destructive operation with zero annotation coverage: no statement of irreversibility, no default-scope behavior for the optional instance_id, and no hint about what the call returns.

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%, so both parameters are already documented. The description does add value with a concrete glob example ('file:*' deletes all file summaries), which goes beyond the schema's bare 'supports glob'. However, the optional instance_id parameter and its default scoping behavior are never addressed.

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?

States a specific verb and resource: 'Delete one or more cached context entries', with an explicit scope qualifier ('cached'). It does not, however, distinguish itself from siblings like recall_context, remember_context, or cache_set, so an agent must infer the boundary from the name alone.

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

Usage Guidelines4/5

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

Gives a concrete trigger condition: 'Use when context is stale or you want to force a fresh analysis.' That is a usable when-to-use signal. It stops short of naming alternatives or an explicit when-not-to-use case, and doesn't warn against deleting entries an active session still depends on.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.