Skip to main content
Glama
furui

furui

Stats

stats

Summarize long-term memory store counts, score distribution, prunable entries, and configuration settings to monitor stored agent memory and pruning needs.

Instructions

Summary of the memory store: counts, score distribution, prunable counts, config.

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

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does signal an inventory-style read by listing what is summarized, implicitly ruling out mutation. However, it says nothing about cost, whether "prunable counts" are a snapshot tied to the prune sibling's criteria, or that config is exposed read-only. Those omissions matter for a zero-annotation tool.

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 front-loaded sentence with no filler, and the four content categories are packed efficiently. "Config" is the one under-specified item, slightly weakening an otherwise tight line.

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?

This is a parameterless summary tool with an output schema, so the description need not explain return shapes; it only has to convey scope, which it does. Everything an agent needs to call it correctly is present.

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 schema takes no parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. There are no options, filters, or scope arguments that would need explanation.

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?

"Summary of the memory store" names the resource and the kind of output (counts, score distribution, prunable counts, config), which cleanly separates it from the action-oriented siblings (remember, recall, forget, prune). It stops short of a precise verb like "report" or "inspect", but the read-only inventory intent is unmistakable.

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?

The description never says when to call this tool or how it relates to alternatives. There is no hint that it is the right choice before deciding what to prune, or that it returns nothing actionable on its own. An agent must infer usage entirely from the name and the enumerated contents.

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