Skip to main content
Glama

Search development memory

search_dev_memory

Search agent transcripts, changesets, and shared development memory to retrieve evidence relevant to a question, enabling reuse of prior context before editing or reviewing code.

Instructions

Purpose: Search imported agent transcripts, changesets, and shared development memory for evidence relevant to a question. When to use: use this before editing, reviewing, or explaining repo behavior so the agent can reuse prior context. Inputs: query is the natural-language search text; mode selects keyword, vector, or hybrid retrieval; filters scope the search by workspace or source; rerank can improve ranking. Side effects: records an MCP audit event. Output: compact search hits with snippets, scores, sources, and evidence references. Failure modes: invalid mode raises an error; vector or hybrid search requires an embedding provider and database connectivity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoRetrieval mode: keyword for lexical search, vector for embeddings, hybrid for both.keyword
limitNoMaximum number of search results to return.
queryYesNatural-language question or keywords to search for in shared memory.
rerankNoReranking strategy: none, local, or api depending on configured providers.none
sourceNoOptional imported source filter such as codex, vscode, claude-code, or manus.
workspace_uriNoOptional workspace root URI used to restrict results to one repo.
candidate_limitNoOptional number of pre-rerank candidates to retrieve before trimming to limit.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries full weight. It discloses side effects (records an MCP audit event) and failure modes (invalid mode raises error, vector/hybrid require embedding provider and database connectivity). It does not explicitly state read-only nature but implies it.

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 highly structured with clear sections (Purpose, When to use, Inputs, Side effects, Output, Failure modes). Each sentence serves a purpose, and the content is front-loaded and efficient.

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?

Given the presence of an output schema (not shown but indicated), the description does not need to explain return values. It covers purpose, usage, inputs, side effects, and failure modes comprehensively 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 description coverage is 100%, so baseline is 3. The description groups parameters (query, mode, filters, rerank) but adds only incremental value beyond the schema. It does not provide new details for individual parameters except high-level context.

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 clearly states the tool searches imported agent transcripts, changesets, and shared development memory for evidence. It uses a specific verb ('search') and resource, and the sibling tools do not overlap in functionality, making it well-differentiated.

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?

The description explicitly says when to use: before editing, reviewing, or explaining repo behavior to reuse prior context. While it does not mention when not to use or alternatives, the context is clear and actionable.

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/geondongkim/geond-agent-protocol'

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