Skip to main content
Glama

search_memory

Search the active ContextDrop project memory when the conversation involves project-specific knowledge that may already be stored. Use this proactively when existing decisions, architecture, requirements, constraints, conventions, preferences, workflows, or other durable project context could affect the response. Do not ask the user to repeat information that can be retrieved from memory. Consider freshness and verify older or potentially outdated memories when necessary.

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_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 behavioral burden. It discloses proactive retrieval, avoidance of redundant user questions, and freshness verification, but it does not describe result format, ranking, scope boundaries, or failure behavior.

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?

The description is front-loaded with the core action and usage condition, and it avoids significant repetition. The list of knowledge types is somewhat long, but it remains readable and purposeful.

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

Completeness3/5

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

For a low-complexity tool with one parameter and no output schema, the description provides useful when/why guidance. However, it is still missing query semantics and any indication of what search results look like, leaving important gaps.

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?

There is only one required 'query' parameter and 0% schema description coverage. The description implies the string is a search query but adds no syntax, scope, examples, or guidance on what the query should contain.

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 gives a specific verb ('Search') and resource ('active ContextDrop project memory'), and it lists the types of project knowledge covered. It does not explicitly differentiate this tool from siblings such as get_project_context, so it falls short of 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 clear proactive when-to-use guidance: use it when project-specific knowledge may already be stored, do not ask the user to repeat retrievable information, and verify older memories. It lacks explicit when-not-to-use rules or named alternatives, so 4 rather than 5.

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.

Resources