Memory MCP

list_memories

Lists stored memories by project and optionally includes inactive facts to audit superseded or expired knowledge.

Instructions

List stored memories, optionally filtered to a project.

Set include_inactive to also show superseded/expired facts (useful for auditing how beliefs changed over time).

How to resolve the project_name

Same as remember: auto-match if unambiguous. If ambiguous, call list_projects() and explicitly ask the user to choose. Once chosen, session-lock it.

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

Name	Required	Description	Default
`project_name`	No
`include_inactive`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 31, 2026

TDQS

A3.8/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 behavioral disclosure burden. It usefully explains that include_inactive reveals superseded/expired facts, but it does not explicitly state that the operation is read-only, whether permissions are required, or whether results are paginated.

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?

The description is front-loaded with the core purpose and then supplies parameter-specific guidance. It is reasonably concise, though the project_name resolution section is somewhat verbose for a list tool.

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?

With an output schema present, the description need not explain return values. It covers purpose, optional filtering, inactive-record behavior, and project resolution, leaving only minor gaps around pagination and explicit read-only semantics.

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 description coverage is 0%, so the description must compensate for both parameters. It does so well: project_name is explained as an optional filter with a resolution protocol, and include_inactive is explained as showing superseded/expired facts.

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?

The description clearly states a specific verb and resource: listing stored memories, with an optional project filter. It is easy to distinguish from mutation siblings like remember or update_memory, but it does not explicitly distinguish itself from recall, which may also retrieve memories.

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 clear usage context for include_inactive, including the auditing use case, and provides an explicit fallback path for resolving ambiguous project_name via list_projects(). It does not explain when to use this instead of recall, but otherwise the guidance is strong.

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

Deploy Server