Skip to main content
Glama

memory_list

Lists valid direction-layer memories grouped by kind so you can review which constraints, designs, directives, and preferences dispatched agents will inherit.

Instructions

List direction-layer memories — valid entries by default, grouped by kind.

Return the current context's direction-layer entries: global + user global entries + the current project's project- level entries, ordered by kind priority (constraint>design>directive>preference) + time descending. This is the same data source as the dual hooks' resident injection; use it to review "what dispatched agents will inherit".

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
kindNooptional, filter by kind (constraint/design/directive/preference)
include_invalidatedNowhether to include invalidated entries (default no)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.2

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden and does meaningful work: it states the default validity filter, the scope composition (global + user global + current project), the sort order (kind priority then time descending), and that this is the same data source as the hooks' resident injection. It does not cover result-size limits or whether any write side effects exist, but the read-only nature is strongly implied by 'List'.

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 purpose is front-loaded in the first clause and the remaining sentences add ordering and scope context rather than filler. Minor deductions for a broken word-wrap artifact ('project-' split across lines) and quoted internal jargon, but no sentence is truly 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?

The tool is a simple read with two optional params and an output schema, so return values need not be explained. The description covers scope, defaults, and ordering adequately; the only remaining gap is the relationship to the sibling memory_search, which would help an agent choose correctly.

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 description coverage is 100%, so both parameters (kind, include_invalidated) are already documented in the schema and the baseline is 3. The description reinforces the meaning of the invalidated filter by stating 'valid entries by default' and explains the ordering, but adds no filter syntax or enum detail beyond what the schema 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?

The description opens with a specific verb and resource ('List direction-layer memories'), states the default scope ('valid entries by default, grouped by kind'), and then expands on ordering and which scopes are included. It is clear what the tool returns, though 'direction-layer' is internal jargon and the description never distinguishes it from the sibling memory_search, which an agent could plausibly confuse it with.

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?

One usage cue is given: 'use it to review "what dispatched agents will inherit"', which anchors the tool to a review/inspection scenario. However, there is no exclusion guidance (e.g., when to prefer memory_search for targeted lookup) and no stated prerequisites, so the when-to-use framing is implied rather than explicit.

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

Deploy Server

Other Tools