Skip to main content
Glama

memory_search

Search persistent local memory for project notes, verified fixes, limitations, and preferences. Filter to verified entries only to avoid treating unverified proposals as facts.

Instructions

Search persistent local memory (project notes, verified fixes, limitations, preferences).

Memory is a local SQLite file - nothing leaves this machine. Unverified entries are proposals, not facts; pass include_unverified=False to get only verified ones.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
scopeNo
projectNo
include_unverifiedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real value: it discloses that memory is a local SQLite file, that nothing leaves the machine, and that unverified entries are proposals rather than facts. It does not state that the operation is read-only, nor describe result ordering, pagination, or what a match looks like.

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?

Two short sentences, front-loaded with the core action and followed by the trust/privacy caveat. The parenthetical content list earns its place; nothing is padded.

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

Completeness2/5

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

For a five-parameter tool with no annotations and no output schema, the description covers privacy and verification semantics but leaves the majority of parameters and the shape of results unexplained. An agent could call it, but not confidently tune scope, project, or limit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, and the description explains only include_unverified. The meaning and expected format of query, scope, project, and limit are left entirely undocumented, which is a significant gap for a search tool where scope and project likely determine result sets.

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?

States a specific verb (search) and resource (persistent local memory) and enumerates the content types stored (project notes, verified fixes, limitations, preferences). It is clear what the tool does, though it does not explicitly contrast itself with siblings like memory_list or memory_note.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance and names no alternative tool, so an agent cannot tell from this text whether to search, list, or note. The only conditional advice ('pass include_unverified=False') is parameter-level, not tool-selection guidance.

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