Skip to main content
Glama
cortex-local-memory

cortex-local-memory

cortex_memory_search

Search local memory entries by query to retrieve ranked snippets from your notes and code.

Instructions

Search memory entries in the cortex knowledge base

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

Input Schema

NameRequiredDescriptionDefault
queryYesThe query to search memories
top_kNoNumber of results to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it discloses nothing about read-only safety, whether search is semantic or keyword-based, ranking/scoring of results, or whether access is scoped to a project/workspace. Only the bare operation is stated.

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 front-loads the verb and resource with zero filler. It is efficient, though its brevity reflects under-specification rather than tight editing.

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 two-parameter retrieval tool with no annotations and no output schema, the agent still lacks the result shape (what fields come back, whether scores are included) and any sense of ranking or scope. The definition is technically usable but leaves material gaps.

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 both `query` and `top_k` are already documented in the schema. The description adds no extra meaning such as default top_k value, maximum allowed, or query syntax, so the baseline of 3 applies.

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?

"Search memory entries in the cortex knowledge base" gives a clear verb (search) plus a specific resource (memory entries) and scopes it to the cortex KB. It is implicitly distinguishable from siblings like cortex_code_search by the word "memory", though the description never names or contrasts an alternative.

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 guidance on when to use this versus cortex_code_search, cortex_search, or cortex_context, and no stated preconditions. The agent must infer the choice purely from the tool name and the noun "memory".

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