Skip to main content
Glama

Memory List

localnest_memory_list
Read-onlyIdempotent

List stored memories from your local AI agent with filters for scope, kind, and status to organize and retrieve project-specific information.

Instructions

List stored memories with optional scope and kind filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoknowledge
statusNoactive
project_pathNo
topicNo
limitNo
offsetNo
response_formatNojson

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
metaNo

Implementation Reference

  • The handler function for 'localnest_memory_list' which calls `memory.listEntries` and normalizes the result.
    async ({ kind, status, project_path, topic, limit, offset }) => normalizeMemoryRecallResult(
      await memory.listEntries({
        kind,
        status,
        projectPath: project_path,
        topic,
        limit,
        offset
      })
    )
  • The tool registration block for 'localnest_memory_list' including input schema definitions.
    registerJsonTool(
      ['localnest_memory_list'],
      {
        title: 'Memory List',
        description: 'List stored memories with optional scope and kind filters.',
        inputSchema: {
          kind: MEMORY_KIND_SCHEMA.optional(),
          status: MEMORY_STATUS_SCHEMA.optional(),
          project_path: z.string().optional(),
          topic: z.string().optional(),
          limit: z.number().int().min(1).max(200).default(20),
          offset: z.number().int().min(0).default(0)
        },
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
          openWorldHint: false
        }
      },
      async ({ kind, status, project_path, topic, limit, offset }) => normalizeMemoryRecallResult(
        await memory.listEntries({
          kind,
          status,
          projectPath: project_path,
          topic,
          limit,
          offset
        })
      )
    );
Behavior3/5

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

The description mentions 'optional scope and kind filters,' adding context about filtering capability beyond the annotations. However, with readOnlyHint and idempotentHint already declared in annotations, the description misses opportunities to explain pagination behavior (limit/offset), the 'status' lifecycle filter, or response format options.

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 single-sentence description is efficiently structured and front-loaded with the verb 'List.' However, given the complete lack of schema documentation and tool complexity, the brevity becomes a liability rather than a virtue.

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 tool with 7 parameters (including pagination and enums), 0% schema coverage, and numerous sibling memory tools, the description is insufficient. The existence of an output schema mitigates return value documentation needs, but the description must compensate for the undescribed parameters and clarify tool selection strategy, which it does not.

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?

With 0% schema description coverage across 7 parameters, the description fails to compensate adequately. It only implicitly references 'kind' and possibly 'project_path'/'topic' via 'scope and kind filters,' leaving 'status', 'limit', 'offset', and 'response_format' completely undocumented and opaque to the agent.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool lists 'stored memories' with 'optional scope and kind filters,' providing a clear verb and resource. However, it fails to differentiate from sibling tools like 'localnest_memory_get', 'localnest_memory_recall', or 'localnest_memory_events', leaving the agent uncertain which memory retrieval tool to select.

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 provides no guidance on when to use this tool versus the 15+ sibling memory tools (e.g., when to 'list' vs 'get' vs 'recall'). There are no stated prerequisites, exclusions, or workflow context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wmt-mobile/localnest'

If you have feedback or need assistance with the MCP directory API, please join our Discord server