Skip to main content
Glama
cortex-local-memory

cortex-local-memory

cortex_stats

Return Cortex statistics such as documents, chunks, vectors, storage usage, current plan, and limits to inspect memory usage and plan capacity.

Instructions

Return Cortex statistics: documents, chunks, vectors, storage usage, current plan and its limits.

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

Input Schema

NameRequiredDescriptionDefault
verboseNoInclude per-extension breakdown

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?

With no annotations, the description carries the full burden, and it does disclose what data comes back (documents, chunks, vectors, storage, plan limits), which is genuine added context for a tool with no output schema. It does not say whether reads are live or cached, whether admin privileges are required, or how costly the call is, so the disclosure is partial.

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?

One front-loaded sentence with a colon-delimited list of returned metrics; no filler or repetition. It could have been split to surface the verbose mode, but nothing present is wasted.

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 one-optional-param read-only tool with no output schema, the description covering the returned metric families is largely sufficient. It still leaves the verbose flag's behavior and any permission or cost constraints unstated, so it is adequate rather than complete.

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 coverage is 100%, and the single parameter 'verbose' is fully documented in the schema as 'Include per-extension breakdown'. The description adds nothing about it — no mention of the verbose mode or its effect. Baseline 3 applies when the schema does the work.

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 (Return) and resource (Cortex statistics) and enumerates the metric families covered: documents, chunks, vectors, storage usage, current plan and limits. That enumeration implicitly separates it from cortex_health and cortex_plan, though it never names what those siblings do differently.

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 guidance and no named alternative. An agent reading the sibling list (cortex_health, cortex_plan, cortex_context) gets no help deciding whether statistics belong here or in cortex_health. Usage is only weakly implied by the word 'statistics'.

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