Skip to main content
Glama

List memory

list_memory
Read-onlyIdempotent

Show the folders and notes stored in Thread memory, with a per-folder summary for large memories. Pass a folder path to view one folder in full.

Instructions

Show the folders and notes in the user's Thread memory. A big memory comes back as a per-folder summary; pass folder (e.g. "classes/21-127") to see one folder in full.

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

Input Schema

NameRequiredDescriptionDefault
folderNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real behavior the annotations do not: a large memory is returned as a per-folder summary rather than in full, which explains apparent truncation an agent would otherwise misread as missing data.

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?

Two sentences, purpose first, then the parameter behavior, with no filler. The trade-off of summary versus full could be stated even more tersely, but nothing here is wasted.

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 one-optional-parameter read tool with an output schema and full annotation coverage, the description covers the main ambiguity (summary versus full folder view). Minor gap: guidance on how to get a folder path or when to fall back to search_memory.

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 0% and the single `folder` parameter has only a default in the schema, so the description must carry the meaning. It does give the effect of passing it (one folder in full) and a path-style example ("classes/21-127"), but it never states what an empty value does or how folder paths are discovered.

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 gives a clear verb and resource: show the folders and notes in the user's Thread memory. That is enough to tell it apart from note/chat readers like read_note or search_memory, though it does not explicitly name a sibling to route against.

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?

It implies the default call lists everything at a summary level and that passing `folder` drills into one folder in full, which is useful call-shaping guidance. It does not say when to prefer search_memory or what to do when the user names a note rather than a folder, so alternatives are left to inference.

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