Skip to main content
Glama
Sign In
Cachly — AI Cognitive Brain

Cachly — AI Cognitive Brain

by cachly-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

forget_context

Delete stale or unwanted cached context entries to force fresh analysis. Supports glob patterns like "file:*" to remove multiple items in one action.

Instructions

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the destructive nature (delete) and supports glob patterns. However, it does not describe behavior on missing keys, authorization needs, or reversibility. The transparency is adequate but not detailed.

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 two sentences, front-loaded with the purpose, and no extraneous information. Every sentence is earned and succinct.

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

Completeness4/5

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

Given the tool's simplicity (two required parameters, no output schema, no nested objects), the description covers the essential information. It could mention return value or error states, but it is complete enough for a basic delete operation.

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% with clear descriptions for both parameters. The tool description does not add any new semantic information beyond what is in the schema. Baseline score of 3 is appropriate.

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?

The description clearly states the tool deletes one or more cached context entries, which is a specific verb+resource combination. It distinguishes from sibling tools like cache_delete by specifying 'cached context entries' rather than generic cache.

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?

The description provides explicit usage guidance: 'Use when context is stale or you want to force a fresh analysis.' It also gives an example of glob pattern usage. However, it does not mention when not to use or list alternatives, but the guidance is clear and context-specific.

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

Deploy Server

Other Tools