Skip to main content
Glama

cachly — Explain it once. Every AI knows it.

list_remembered

List all cached context entries for this project. Shows what knowledge the AI assistant has already cached, so you can decide whether to recall existing context or refresh it. Returns: key, category, size, TTL remaining, and a content preview.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_remembered"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax entries to return (default: 50)
categoryNoFilter by category (default: all)
instance_idNoUUID of the cache instance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 disclosure burden. It partially meets that with a useful return-field preview (key, category, size, TTL remaining, content preview), which is real value since there is no output schema. It does not state explicitly that the operation is non-mutating, how results are ordered, or what happens when the cache is empty or instance_id is omitted — meaningful gaps for an unannotated 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?

Three sentences, front-loaded with the core action, and the return-value sentence is genuinely useful. The middle sentence slightly restates the first ("what knowledge the AI assistant has already cached"), a minor redundancy but not wasteful overall.

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 simple, zero-required-parameter listing tool with full schema coverage and no output schema, the description supplies what an agent needs: what is listed, why, and what fields come back. The remaining gap is behavioral (ordering, empty-state, instance_id semantics) rather than structural.

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 all three parameters (limit, category, instance_id) are already documented with defaults and an enum. The description adds no additional parameter meaning — notably it never explains the relationship between "this project" and instance_id — so the baseline of 3 is appropriate.

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?

"List all cached context entries for this project" gives a specific verb (list), resource (cached context entries), and scope (this project). It is clearly a read-only enumeration rather than a retrieval of content, which distinguishes it in spirit from siblings like recall_context or cache_get, though it never names those alternatives explicitly.

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

Usage Guidelines3/5

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

The description implies usage ("so you can decide whether to recall existing context or refresh it") and thereby hints at the recall/refresh alternatives, but it does not name a specific sibling tool or state when-not to use this one. The guidance is inferable rather than explicit.

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.