Skip to main content
Glama
Sign In
recall-kit

recall-kit

by sibrahimpa1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

memory_stats

Returns the memory store's location and entry counts, plus the server process ID, so you can verify that a fresh session sees the expected persisted memory.

Instructions

Store location and counts (plus the server process id, useful to prove fresh sessions).

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

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral load: it does disclose the content of the response (location, counts, process id) and hints at a session-freshness use case. It does not state that the call is side-effect free or read-only, and an output schema already covers return values, so what remains is partial rather than rich disclosure.

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?

A single short sentence with no filler, but the front-loaded phrase is genuinely ambiguous about what the tool does, so the brevity costs clarity rather than serving it.

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 trivial to invoke (no parameters, output schema present) so the description needn't explain return format. What is missing is intent: why an agent should call this instead of memory_recall, which leaves the definition only minimally complete for selection purposes.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description adds no parameter context, but none is needed for an empty argument object.

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

Purpose3/5

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

"Store location and counts (plus the server process id...)" reads as a description of returned data rather than a clear verb+resource statement of what the tool does. Combined with the name memory_stats an agent can infer it reports statistics, but the sentence never says "retrieve" or "report", and "Store" is easily misread as an imperative verb.

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 explicit when-to-use guidance, no prerequisites, and no reference to any sibling such as memory_recall or memory_history. The parenthetical "useful to prove fresh sessions" is the only hint of a use case, and it is incidental rather than directive.

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

Deploy Server

Other Tools