Skip to main content
Glama

memory_list

Read-only

Lists every saved memory with its type and a one-line summary so you can see what is known. Filter by type: user, feedback, project, or reference.

Instructions

List every saved memory with its type and one-line description. Start here to see what is known.

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": "memory_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOnly list memories of this type.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations only supply readOnlyHint=true, so the description carries the rest of the burden. It does disclose the return shape (type and one-line description) and the apparent completeness of the listing, but says nothing about ordering, volume limits, or how the optional type filter interacts with "every".

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 short sentences, zero filler, with the core action front-loaded before the orienting hint. Nothing is redundant.

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 read-only enumeration tool with a fully documented single parameter and clear annotations, this is nearly sufficient. The only shortfall is not mentioning the optional type filter, which the schema covers anyway.

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 coverage is 100% and the single type parameter is fully documented with an enum, so the baseline of 3 applies. The description adds no filtering semantics beyond what the schema already provides.

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?

States a specific verb and resource ("List every saved memory") and adds what each entry carries (type plus a one-line description). It does not explicitly distinguish itself from siblings like memory_recall or memory_get, but the "start here" framing positions it as the enumeration entry point.

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?

"Start here to see what is known" implies this is the first-call overview tool, which is genuine usage guidance. However, it never states when to prefer memory_recall or memory_get instead, and no exclusions are given.

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

This server cannot be deployed

Other Tools