Skip to main content
Glama

memory_search

Search the AI Team OS memory store by keywords to retrieve relevant stored memories, with optional scope and limit controls for narrowing results to a user, project, or system context.

Instructions

Search the memory store in AI Team OS.

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
limitNoMaximum number of results, default 10
queryNoSearch keywords
scopeNoMemory scope, default "global"global
scope_idNoScope ID; when **left empty**, the server derives it from the context (global→system, user→user, project→the current project or an unregistered directory's fingerprint temporary bucket). Pass it explicitly only when a precise cross-scope specification is needed (e.g. a team's scope_id).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.2

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: not that it is read-only, not whether results are ranked or how, not what the limit applies to, and not what happens when query is empty. The only behavioral detail present lives in the scope_id schema text, not the description.

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 short sentence that is front-loaded and contains no filler. It is efficient, though its brevity borders on under-specification rather than true conciseness.

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?

WAIT_CORRECTION

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 the scope/scope_id fields are documented in detail in the schema, so the schema does the heavy lifting. The description adds no meaning beyond it — no guidance on how query is matched (substring, keywords, semantic) or how limit interacts with ranking.

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 ("Search the memory store"), so the agent knows exactly what operation it performs. It does not distinguish this from sibling retrieval tools such as unified_search, memory_list, or ecosystem_search, which is the only gap at this level.

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?

There is no when-to-use guidance at all: nothing says when to pick memory_search over memory_list (which presumably enumerates without a query) or unified_search (which presumably spans more stores). With no required parameters and a defaulted empty query, an agent gets no signal about what a search with no keywords even does.

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