Skip to main content
Glama
cortex-local-memory

cortex-local-memory

cortex_suggest

Returns search suggestions from partial queries and current context, using prefetched cache or local search to help coding agents complete queries quickly.

Instructions

Get smart search suggestions based on partial query and current context. Returns instant results from prefetched cache or fast search.

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

Input Schema

NameRequiredDescriptionDefault
queryYesThe partial query to get suggestions for
top_kNoNumber of suggestions to return
current_fileNoCurrent file path for context-aware suggestions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.1

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden, and it does disclose a useful behavioral trait: results come from a prefetched cache or a fast search, which implies low latency and possible cache staleness. It says nothing about read-only safety, permissions, result freshness guarantees, or the response shape, and these omissions leave notable gaps for a tool with no annotation coverage.

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?

Two tight sentences with the purpose front-loaded and the return behavior second. 'Smart' and 'instant' are mild marketing adjectives that do not add much, but the rest of the wording is efficient and non-redundant.

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?

The tool is a simple three-parameter read operation with fully documented parameters and no output schema, and the description covers the essentials for calling it. It does not describe what a suggestion object contains or how results are ordered or limited, and it does not state cache staleness caveats, so an agent lacks some information needed to interpret the output.

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 the schema already explains query, top_k, and current_file. The description adds only a little meaning beyond that: 'partial query' clarifies that query is a prefix rather than a complete string, and 'current context' hints at the role of current_file. No detail is added on formatting, defaults, or limits.

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 uses a specific verb and resource: 'Get smart search suggestions based on partial query and current context.' That is clear enough for an agent to distinguish it from a full search tool such as cortex_search. It stops short of naming a sibling to contrast with, so it is a 4 rather than 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The mention of a 'partial query' implies the autocomplete/suggestion scenario, where the agent should call this tool while text is being built. However, the description never states when to prefer this tool over cortex_search or cortex_code_search, and it gives no exclusion rules. The usage guidance is therefore only implied.

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