Skip to main content
Glama
persistent-memory-mcp

persistent-memory-mcp

Search memory

memory_search
Read-onlyIdempotent

Search stored facts, decisions, and procedures by keyword before answering about earlier user statements. Returns only current, valid versions; excludes withdrawn, superseded, or expired entries.

Instructions

Find stored facts, decisions and procedures by keywords. Use it before answering about anything the user said or decided earlier. Returns only current, valid versions, each with its text, kind, artifact_id and exact ref; withdrawn, superseded and expired versions are left out, and an empty list means nothing valid matches. Read-only. To re-read one version you already hold, use memory_read.

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": {
      "query": "<query>"
    },
    "name": "memory_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoUTC time to check validity at. Leave out for now.
kindsNoOnly these kinds. Leave out to search all.
queryYesKeywords or a question.
top_kNoMaximum number of results, default 5. Leave out unless you need more.
max_charsNoMaximum characters of text returned in total, default 2000.
conditionsNoFacts about the current situation, matched exactly against stored preconditions. Leave out unless the user describes a situation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, the description discloses that only current, valid versions are returned and that withdrawn, superseded, and expired versions are excluded. It also explains that an empty list means nothing valid matches, which is important behavioral context for interpreting results.

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 short, front-loaded with purpose, then usage, return behavior, and the alternative tool. Every sentence contributes useful information with no unnecessary wording.

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

Completeness5/5

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

There is no output schema, but the description explicitly lists returned fields and explains filtering and empty-result semantics. Given the rich parameter descriptions, this is complete enough for an agent to call and interpret the tool correctly.

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 parameters such as as_of, kinds, top_k, max_chars, and conditions in detail. The description adds only the broad keyword-search framing, which is consistent with but not materially richer than the schema.

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 states a specific verb and resource: finding stored facts, decisions, and procedures by keywords. It also clearly distinguishes the tool from memory_read, which is for re-reading one known version, so an agent can select it without opening the schema.

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

Usage Guidelines5/5

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

It gives explicit timing guidance: use it before answering anything the user said or decided earlier. It also names memory_read as the alternative for re-reading a version already held, creating a clear routing rule.

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