Skip to main content
Glama

SourceGeek

List memories

list_memories
Read-only

List long-term memories: the current user's personal ones and the workspace-shared ones. Pass keys to read those memories in full, or query to get the ones matching a topic; with neither, lists everything.

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_memories"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysNoExact memory keys to read, from the saved key index.
queryNoWhat the memories to find are about, in any words, e.g. 'acme hiring bar'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds that results span two visibility scopes (personal and workspace-shared) and that keys returns full memory content while query returns topic matches. It stops short of describing result shape, ordering, or volume/pagination limits when listing everything.

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?

A single sentence split by a colon and semicolons, front-loaded with the resource and scope, then the three usage modes in the order an agent would consider them. No filler or redundant restatement of the title.

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 two-optional-parameter, read-only list tool with no output schema, the description covers scope, mode selection, and the default case, which is nearly everything needed to invoke it correctly. The remaining gap is what the listing output contains (keys only vs summaries), which matters when no parameters are passed.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description meaningfully adds the semantics the schema does not: keys yields full memories, query yields topic matches, and omitting both is the list-all default. That interaction/default behavior is genuine value beyond the property descriptions.

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?

"List long-term memories" is a specific verb+resource, immediately scoped to "the current user's personal ones and the workspace-shared ones", so the agent knows exactly what corpus is covered. No sibling tool in the catalog handles memories, so no further differentiation is needed.

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?

The description gives explicit mode-selection rules: use keys to read specific memories in full, use query to find memories by topic, and use neither to list everything. Each of the three invocation paths is spelled out with its condition, leaving nothing to inference.

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.

Resources