Skip to main content
Glama
cortex-local-memory

cortex-local-memory

cortex_search

Find relevant notes and code by searching a local knowledge base with vector and full-text search, returning ranked chunks for your query.

Instructions

Search the local knowledge base (cortex) using vector and fts and return relevant chunks

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

Input Schema

NameRequiredDescriptionDefault
queryYesThe exact search query to lookup
top_kNoNumber of results to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does add real behavioral signal by disclosing that retrieval is hybrid (vector + fts) and that results come back as chunks, but it says nothing about ranking/score fusion, ordering, default result count, or any limits or permission requirements.

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 compact sentence with no filler, and the core purpose plus return type are front-loaded. The unexpanded "fts" acronym and the vague "relevant chunks" phrase cost it a perfect score.

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 two-parameter, annotation-free search tool with no output schema, the description covers the essentials of what it does and roughly what it returns. It is still thin on result ordering, pagination/defaults, and how it relates to the other cortex search entries, which an agent needs to invoke it correctly.

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 parameters are already documented in the input schema and the baseline is 3. The description adds nothing about the query format or what top_k defaults to or caps at, so it does not exceed the schema.

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?

States a specific verb ("Search") and resource ("local knowledge base (cortex)") and even names the retrieval strategy (vector + fts) and return type (chunks). It does not, however, distinguish itself from similar siblings such as cortex_code_search or cortex_memory_search, so an agent cannot tell which search surface covers what without inspecting them.

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 or when-not-to-use guidance, and no mention of the sibling search tools that overlap with this one. "Local knowledge base" implies a general-purpose KB search, but with five-plus search-like siblings the routing decision is left entirely to inference.

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