Skip to main content
Glama
cortex-local-memory

cortex-local-memory

cortex_map

Map your local knowledge base to view document counts, file-type breakdowns, and sample paths, so you can identify what is indexed before searching.

Instructions

Get a map of the local knowledge base: document count, file type breakdown and sample paths. Use this first when you do not know what is indexed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cortex_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax number of file types / paths to list (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. 'Get' plus the read-only nature of a map/overview strongly implies a safe non-mutating call, and it usefully discloses the return contents (counts, breakdown, sample paths), but it says nothing about cost, whether indexing must have occurred first, or the difference between the local knowledge base here and whatever 'local' means in sibling tools.

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?

Two compact sentences: what it returns, then when to call it. The orientation guidance is placed last where it belongs and nothing is repeated from the schema or title.

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

Completeness4/5

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

This is a low-complexity read tool with one optional parameter and no output schema, so the description's enumeration of return contents does the work an output schema would otherwise do. Missing only edge details such as behavior on an empty or unindexed knowledge base and whether output is truncated beyond limit.

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?

With a single optional parameter at 100% schema coverage, the schema already explains that limit caps the number of file types/paths listed. The description's mention of 'file type breakdown and sample paths' reinforces what limit governs but adds no format, ordering, or truncation behavior beyond the schema text.

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 and resource ('Get a map of the local knowledge base') and enumerates exactly what comes back: document count, file type breakdown, and sample paths. It does not name or contrast with neighbors like cortex_stats or cortex_context, so an agent must infer from scope rather than explicit differentiation.

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 an explicit ordering rule — 'Use this first when you do not know what is indexed' — which is a real orientation cue for an agent entering an unknown corpus. There is no when-not guidance and no named alternative for cases where the agent already knows what is indexed.

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