Skip to main content
Glama

Search memories

search_memories
Read-only

Search past conversation memories for relevant context. Use this when the user references past work, previous troubleshooting, earlier decisions, or asks 'did we already do X?'. Returns relevant facts and insights from prior conversations.

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

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query describing what to look for in past conversations

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The readOnlyHint annotation already declares this is a non-mutating read, so the description carries a lighter burden. It adds useful context that results are "facts and insights from prior conversations," but says nothing about result volume, ranking, recency, or whether an empty result is meaningful. Additive but thin.

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?

Three short sentences, front-loaded with the core action and then the trigger conditions. Every sentence contributes — none merely restates the tool name or title.

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 one-parameter read-only tool with annotations covering the safety profile and no output schema, the description supplies enough: what it searches, when to call it, and roughly what comes back. A note on result scope or limits would close the remaining gap.

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% for the single required `query` parameter, so the schema already explains it. The description adds only the domain framing (what is being searched) and no guidance on query phrasing, breadth, or keyword vs. natural-language style. Baseline 3 is appropriate.

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 uses a specific verb+resource pair ("Search past conversation memories") and scopes it to "relevant context," so an agent immediately knows what is retrieved. It stops short of differentiating itself from adjacent tools in the catalog such as save_memory or the various *_search tools, so it is not quite 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 Guidelines4/5

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

It gives concrete invocation triggers: the user referencing past work, previous troubleshooting, earlier decisions, or asking "did we already do X?". That is unusually actionable guidance. It provides no exclusions or negative conditions (e.g., when to prefer a code or log search instead), which keeps it out of 5 territory.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.