Skip to main content
Glama

list_memories

Read-only

Retrieve stored memories newest first, filtering by tag, fact or episode type, and active or superseded status; use pagination to browse results.

Instructions

Lista memorias, las más recientes primero.

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
tagNoSolo con esta etiqueta.
kindNoSolo fact o solo episode.
limitNoTamaño de página.
cursorNonext_cursor de la página anterior.
statusNoactive o superseded (reemplazadas).

Output Schema

NameRequiredDescriptionDefault
itemsYes
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 and openWorldHint=false, so the safety profile is covered by structured data. The description's one added behavioral fact is the sort order (most recent first), which is genuinely useful. It says nothing about pagination behavior or total counts, though the schema's cursor field implies paging.

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 clause with zero filler, and the ordering constraint is front-loaded right after the verb. It is efficient, though so terse that it reads as underspecified rather than deliberately compact.

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 full schema coverage, complete annotations, and an output schema, the description covers purpose and ordering adequately. The gap is the absence of any guidance on how this differs from recall or history, which matters given five closely related siblings.

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%, and every parameter (tag, kind, limit, cursor, status) carries its own description in the schema, so the baseline is 3. The description adds no filtering semantics or interaction notes beyond what the schema already documents.

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 ("Lista memorias") and adds the ordering guarantee ("las más recientes primero"), so the agent knows exactly what operation this performs. It does not distinguish the tool from siblings such as recall or history, which keeps it out of the top band.

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?

Usage is only implied: "Lista memorias" suggests browsing the memory store, reinforced by sibling names like recall and history. There is no explicit when-to-use or when-not-to-use statement, and no routing toward an alternative tool for filtered or relevance-ranked lookups.

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