Skip to main content
Glama

memory_stats

Read-only

Get project-scoped memory statistics broken down by kind, status, and scope, plus vector index status, to audit what your AI coding agents have stored.

Instructions

查看项目记忆统计(按 kind/status/scope 分布 + 向量索引状态)。project 必填(HTTP 模式下报错会附带项目列表供确认当前项目)。

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

Input Schema

NameRequiredDescriptionDefault
projectNo项目名或 id。省略时从当前工作目录自动解析

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.4

TDQS

A3.5/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes that this is a safe read, so the description does not need to restate that. It adds real behavioral context by naming what the response contains: breakdowns by kind/status/scope and index health. It also discloses a failure mode: in HTTP mode, an error carries the project list, so the agent can recover. Pagination and cost are not discussed, but the main gaps are covered.

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 compact sentences with no filler. The core purpose is front-loaded, and the HTTP-mode caveat follows as a useful parenthetical. The parenthetical is slightly dense but earns its place.

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?

There is no output schema, so the description must convey what comes back; it does so by listing the breakdown dimensions and index status. For a single-parameter read tool, this is nearly complete. The only deficiency is how it handles the optional-project case, which directly contradicts the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; however, the description actively conflicts with the schema. It says project is required ("project 必填"), while the schema lists it as optional, because omitting it auto-resolves from the current working directory. That contradiction can mislead an agent into always supplying a value unnecessarily, so this score falls below the baseline.

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 and resource: view project memory statistics, with the content spelled out (distribution by kind/status/scope plus vector index status). That is far more informative than the name alone, but it never distinguishes this tool from siblings such as memory_index or memory_review.

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?

Usage is only implied: an agent can infer that this tool is for inspecting aggregates rather than records, but the description never states when to choose it over memory_index or memory_search, and it gives no prerequisites or exclusions.

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