Skip to main content
Glama
mergestorm-mcp

mergestorm-mcp

Official

List memories

list_memories
Read-onlyIdempotent

Review and retrieve stored user memories newest first with IDs, filtering by scope, repository, or kind so you can inspect and delete what is retained.

Instructions

List what Mergestorm remembers about the user, newest first, with each memory's id. Filter by scope (user or repo), repo (owner/repo) or kind. Works with memory off, so the user can still see and delete what is stored.

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
kindNo
repoNo
scopeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.31

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful context beyond those annotations: results are newest first, each memory's id is included, and listing still works when memory is off so users can inspect and delete stored data.

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?

Two tight sentences front-load the core behavior and then cover filtering and the memory-off caveat. Every clause adds actionable meaning with no restatement of the title alone.

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?

There is no output schema, but the description states ordering and that ids are returned, which is enough for a simple read-only list tool. The remaining gap is minor: it does not explicitly route between this tool and search_memory.

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 carry parameter meaning. It explains scope as user or repo, repo as owner/repo format, and kind as a filter, covering all three parameters although it does not spell out the kind enum values that the schema already provides.

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 gives a specific verb and resource ("List what Mergestorm remembers about the user") and adds scope, ordering, and returned identifier. An agent can immediately understand that this enumerates stored memories with their ids, distinct from memory search or mode tools.

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 through filtering and the note that it works with memory off, but it does not explicitly say when to choose this over siblings such as search_memory or get_memory_mode. Guidance is inferable rather than stated.

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