Skip to main content
Glama

rr_list_memory_entries

Read-onlyIdempotent

List memory namespace entries, most recently updated first, with pagination and optional key-prefix filtering to review stored records.

Instructions

List the entries stored under a memory namespace, most recently updated first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "namespace": "<namespace>"
    },
    "name": "rr_list_memory_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows per page (default 50, max 200).
cursorNonext_cursor from the previous page. Pass it with the same other inputs until has_more is false.
namespaceYesNamespace to list
key_prefixNoOnly keys starting with this prefix

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered without the description. The description adds real behavioral value by disclosing the sort order (most recently updated first), but says nothing about result volume, pagination semantics, or what an entry contains.

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, covering both the resource and the ordering in one pass. It is perhaps slightly too terse for a tool with pagination and prefix filtering, but nothing is wasted.

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

Completeness3/5

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

For a simple read-only list tool with a fully documented 4-parameter schema and rich annotations, the definition covers purpose and ordering adequately. It leaves the return shape unexplained (there is no output schema) and does not describe the paging loop or default page size, which the description could have summarized.

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 limit, cursor, namespace, and key_prefix are all documented in the schema, including the paging contract for next_cursor/has_more. The description only reinforces the namespace scope and adds no format or filter semantics beyond that, making the baseline 3 correct.

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 names a specific verb and resource ('List the entries stored under a memory namespace') and adds ordering ('most recently updated first'), so an agent can distinguish it from get/delete/save siblings by behavior. It stops short of explicitly naming those siblings, which keeps it from a 5.

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?

Listing entries under a namespace implies the browsing use case, and the required namespace parameter anchors when it applies. There is no explicit when-not guidance or named alternative (e.g., use rr_get_memory_entry for a single key), so the agent must infer the boundary.

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