Skip to main content
Glama

cachly — Explain it once. Every AI knows it.

remember_context

Save context information to the cache so you can recall it later without re-computing. Perfect for caching: codebase overviews, file summaries, project structure, frequently-accessed data, or "thinking" results like dependency analysis. The AI assistant can use this to avoid re-reading the entire codebase every time. Overwrites any existing value stored under the same key. Returns { key, stored_at, ttl } confirming the saved context. Example: remember_context("project overview", "This is a Next.js app with...") then later: recall_context("project overview"). Use recall_context to retrieve; use list_remembered to see all stored keys.

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": {
      "key": "<key>",
      "content": "<content>"
    },
    "name": "remember_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesDescriptive key like "project_overview", "auth_architecture", "file:src/index.ts"
ttlNoTime-to-live in seconds (default: 86400 = 24h, use 0 for no expiry)
contentYesThe context/summary/analysis to remember
categoryNoCategory for organization (default: custom)
instance_idNoUUID of the cache instance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses overwrite semantics ('Overwrites any existing value stored under the same key') and the return shape { key, stored_at, ttl }. It omits persistence scope, size limits, and what instance_id implies behaviorally, leaving real gaps for a mutation tool.

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?

Front-loaded with the operation and its payoff, and the example plus sibling pointers are useful rather than filler. It is somewhat long, with the caching rationale restated twice ('without re-computing' and 'avoid re-reading the entire codebase every time'), which is minor redundancy.

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?

For a 5-parameter write tool with 100% schema coverage and no output schema, the description covers purpose, overwrite behavior, return shape, and the retrieval counterpart. What remains missing are operational constraints such as size limits and cache lifetime semantics beyond the ttl default.

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%, so the schema already documents key, content, ttl, category, and instance_id, and the description adds little parameter-level meaning beyond an example call. The baseline of 3 applies when the schema does the heavy lifting.

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 opens with a specific verb+resource ('Save context information to the cache') and immediately scopes the purpose to later recall, which cleanly separates it from recall_context and list_remembered. An agent can identify the operation without reading the schema.

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?

It gives concrete when-to-use examples (codebase overviews, file summaries, dependency analysis) and explicitly routes retrieval and enumeration to recall_context and list_remembered. It stops short of stating when NOT to use this tool (e.g. large payloads, session-scoped data, or preferring cache_set), so it is clear but not exhaustive.

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.