Skip to main content
Glama
Sign In
Memorable MCP Server

Memorable MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

memorable_list_memories

List, filter, and paginate memories in Memorable using optional query, search mode, and pinned filters to retrieve relevant stored context.

Instructions

List, filter, and paginate memories in Memorable with optional query, mode, and pinned filters

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": "memorable_list_memories"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoOptional search query across memory title and body
modeNoSearch mode: 'auto' (hybrid vector fallback to keyword), 'semantic' (pure pgvector), or 'keyword'
limitNoNumber of memories to return (1-100, default 50)
offsetNoPagination offset (default 0)
pinnedNoFilter memories by pinned status

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses little beyond the surface action. It never states that this is a non-mutating read, how results are ordered, what the response envelope looks like, or what the 1-100 limit and offset imply about total counts and pagination exhaustion.

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?

A single front-loaded sentence with the action first and the optional filters after; there is no filler, hedging, or redundant restatement of the title.

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?

With five optional parameters fully described in the schema and no output schema, the description covers enough for an agent to call the tool correctly. It falls short on ordering, pagination behavior, and the relationship to the search sibling, which matter for a listing endpoint.

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 coverage is 100%, so the schema already documents `q`, `mode`, `limit`, `offset`, and `pinned`, including enum values and defaults. The description's mention of 'query, mode, and pinned filters' restates those parameters without adding interpretation, so the baseline of 3 applies.

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 set (list, filter, paginate) and the exact resource (memories in Memorable), and it enumerates the filter dimensions (query, mode, pinned). It does not, however, distinguish this tool from the sibling `memorable_search`, which an agent would reasonably consider for the same resource.

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: 'optional query, mode, and pinned filters' signals that everything is optional and this is the browsable listing endpoint. There is no explicit when-to-use statement, no when-not, and no pointer to alternatives such as `memorable_search` or `memorable_recall_context`.

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