Skip to main content
Glama
Sign In
Relax Memory MCP

Relax Memory MCP

by jgauffin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_memories

List all memories grouped by category in a hierarchical index to browse stored information.

Instructions

List all memories as a hierarchical index grouped by category.

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

Input Schema

NameRequiredDescriptionDefault
include_descriptionNoInclude description in the index

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden of disclosing behavior. It states the output is a hierarchical index grouped by category, implying a read-only operation, but doesn't explicitly confirm no side effects or describe any return format details beyond grouping. It's adequate but not rich.

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?

The description is a single, front-loaded sentence that directly states the purpose and key output characteristics without any filler or redundancy.

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 low-complexity tool with one optional parameter and no output schema, the description adequately conveys what the tool returns (hierarchical index) and its scope (all memories). It could mention more about the structure of entries, but the available information covers the essential expectations.

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?

The only parameter, include_description, is fully documented in the schema with a clear description and default value. The tool description adds no additional meaning, so the baseline score of 3 is appropriate.

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

Purpose5/5

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

The description uses the specific verb 'List' with the resource 'memories' and clarifies scope as 'all memories' with a 'hierarchical index grouped by category.' This clearly distinguishes it from sibling tools like add_memory, get_memory, and delete_memory, which perform different actions.

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

Usage Guidelines4/5

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

The description implies this tool is for retrieving a full overview of all memories, contrasting with get_memory for individual retrieval. While it doesn't explicitly name alternatives or exclusions, the context makes the appropriate use case clear.

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