Skip to main content
Glama

Search Memory

memorix_search

Search project memory across sessions to retrieve compact, relevant context from past observations. Find specific facts, decisions, or solutions when a full brief is unnecessary.

Instructions

Search project memory. Returns a compact index (~50-100 tokens/result). Do not use as a follow-up to a complete memorix_project_context brief unless a specific fact is still missing or the user asks for deeper history; provide purpose when intentionally expanding. Use memorix_detail to fetch full content for specific IDs. Use memorix_timeline to see chronological context. Searches across all observations stored from any IDE session — enabling cross-session and cross-agent context retrieval.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoFilter by observation type
forceNoUse only when the user explicitly asks to read a record already represented in the latest Autopilot brief.
limitNoMax results (default: 20)
queryYesSearch query (natural language or keywords)
scopeNoSearch scope: "project" (default) only searches current project, "global" searches all projectsproject
sinceNoOnly return observations created after this date (ISO 8601 or natural like "2025-01-15")
untilNoOnly return observations created before this date (ISO 8601 or natural like "2025-02-01")
sourceNoFilter by memory source. "git" returns only commit-derived ground truth memories. Omit for all sources.
statusNoFilter by memory status. "active" (default) shows current memories, "all" includes resolved/archived.active
purposeNoWhy this must expand beyond the latest Autopilot brief. Name the missing fact or the user's explicit request.
qualityNoRetrieval profile: fast stays local, balanced uses configured embeddings, thorough explicitly permits optional LLM refinement.balanced
maxTokensNoToken budget — trim results to fit (0 = unlimited)
Behavior4/5

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

No annotations provided, but description discloses return format (compact index, token size), search scope (cross-session/cross-agent), and it implies read-only behavior. Lacks explicit safety or permission info, but acceptable for a search tool.

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?

Two sentences plus guidance on usage; front-loads purpose, then usage and alternatives. No wasted words, every sentence adds value.

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?

Given 12 parameters, no output schema, and moderate complexity, the description covers purpose, usage, and return characteristics well. Minor gaps: no explanation of purpose field usage or behavior when omitted, but overall complete for a search tool.

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% with descriptions for all 12 parameters. The tool description does not add significant meaning beyond the schema, only gives context on return format. Baseline 3 appropriate.

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?

Clearly states 'Search project memory' with verb and resource, mentions return format as compact index (~50-100 tokens/result), and distinguishes from siblings (memorix_detail, memorix_timeline).

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?

Explicitly warns against using as follow-up to a complete brief unless a specific fact is missing, provides purpose requirement, and names alternatives (memorix_detail for full content, memorix_timeline for chronology).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AVIDS2/memorix'

If you have feedback or need assistance with the MCP directory API, please join our Discord server