Skip to main content
Glama

memory_list

Search and filter durable project memories by category, tag, file path, confidence, or injection mode. Use it to surface confirmed and always-injected entries first when recalling project knowledge.

Instructions

Search or filter durable project memories (always-injected and confirmed entries ranked first).

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
tagNo
queryNo
categoryNo
file_pathNo
confidenceNo
project_idNoOptional project ID (auto-resolved when omitted).
inject_modeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

The parenthetical discloses a genuinely useful non-obvious behavior: always-injected and confirmed entries are ranked first. However, with no annotations present, the description still leaves the read-only/safety profile, result limits, pagination, and default ordering for non-ranked entries undisclosed.

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?

A single front-loaded sentence with no filler; the ranking detail is placed efficiently in a parenthetical. It is concise because it is short, not because it is complete.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a seven-parameter, zero-required search tool with no annotations and no output schema, the definition is far too thin to clarify which combinations of filters are valid or what shape results take. It leaves most of the calling contract unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 14%, with only project_id documented, so the description must compensate for six undocumented parameters (tag, query, category, file_path, confidence, inject_mode) and it does not. The ranking hint loosely gestures at confidence and inject_mode but never explains matching semantics, e.g. whether query is full-text or exact.

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 ("Search or filter") and a specific resource ("durable project memories"), which is enough to distinguish it from memory_save/memory_delete. It stops short of differentiating itself from the similarly-named note_list, so sibling disambiguation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance on when to prefer this tool over memory_save, note_list, or project_list, and no exclusions or prerequisites. Usage must be reverse-engineered from the name alone.

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