Skip to main content
Glama

memory.status

Reports memory health and metadata for the project's agent memory store: file counts, index sizes, pending proposals with age and drift, and security posture. Use this read-only status to decide if maintenance is needed.

Instructions

Report memory health and metadata for the project's .agent-memory/ store: file counts per kind, index + current-state sizes, pending staged proposals (with age, TTL remaining, and drift status per proposal), orphaned branch-local files, secret-scan / git / lock posture. Read-only; never modifies any file. Call this to decide whether memory needs maintenance (stale staging, drifted proposals) before proposing further updates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
memory_versionYesthe agent-memory binary version
repoYesproject name from the manifest
active_branchNocurrent git branch, empty outside a repo
durable_filesYescount of long-lived git-tracked memory files
archive_filesYescount of files under archive/
local_sessionsYescount of session-log files under sessions/
local_current_filesYescount of branch-local current.*.md files
orphan_local_filesNolocal current files whose branch no longer exists
index_size_bytesYessize of the FTS5 shadow index on disk
current_size_bytesYescombined size of the active branch + shared current files
staged_updatesNopending staged proposals with age, TTL, and drift status
stale_notesNofiles flagged stale by freshness tracking (future)
securityYessecret-scan + provenance posture
gitYesgit integration flags
lockYesadvisory-lock state
Behavior5/5

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

No annotations provided, so description fully discloses read-only behavior: 'Read-only; never modifies any file.' Also details what information is reported, giving full transparency.

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 sentences: first lists what is reported, second gives purpose. Front-loaded with main functionality, no redundant or filler content.

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

Completeness5/5

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

Despite no annotations or output schema in the definition, description thoroughly covers the tool's purpose, behavior, and usage context. Output schema exists, so return value details are not needed from description.

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

Parameters4/5

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

No parameters; schema coverage is 100% so no parameter documentation needed. Baseline score of 4 is appropriate as description adds no param info, but none is required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it reports memory health and metadata, listing specific items (file counts, sizes, pending proposals). Differentiates from siblings memory.fetch_context and memory.propose_update, which handle context and updates respectively.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly states when to call: 'to decide whether memory needs maintenance...' and 'before proposing further updates.' Also indicates read-only nature, guiding safe usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/xChuCx/agent-memory'

If you have feedback or need assistance with the MCP directory API, please join our Discord server