Skip to main content
Glama

amem_stats

Retrieve usage and savings stats—local lookup time, estimated tokens or milliseconds saved, and hit rate—for one workspace or all tracked repos, with an optional lookback window.

Instructions

Usage and savings stats (local lookup time, estimated tokens/ms saved, hit rate) for one workspace/repo or everything. Use when asked how much amem helped, how often it hit, or usage over time. All arguments are optional.

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

Input Schema

NameRequiredDescriptionDefault
daysNoLookback window (default 30)
scopeNoall (every tracked repo/workspace) or current (the given workspace / cwd)
workspaceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.5
    • addedInput schema / required
      Added value: +[]
  2. First observedv0.4.2

TDQS

A3.6/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. It does disclose what the tool reports (lookup time, tokens/ms saved, hit rate), which implicitly frames it as a read-only measurement query. It does not explicitly state that it is non-mutating, does not describe cost, latency, or whether stats are cumulative versus per-window, and gives no return format.

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?

The metrics and triggers are front-loaded and the text is tight overall. The final sentence, 'All arguments are optional,' is redundant given the schema already shows no required parameters, but it costs only a few words.

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 stats tool with no output schema, the description does reasonably well by enumerating the metric categories returned. However, it leaves the amem_usage_report overlap unresolved and says nothing about cumulative versus windowed semantics, output shape, or the workspace parameter, so an agent could still call the wrong sibling or pass workspace incorrectly.

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 67%: days and scope are documented in the schema, but workspace has no description anywhere. The description adds only the phrase 'for one workspace/repo or everything,' which loosely maps to scope values, and 'All arguments are optional,' which merely restates required=[]. It does not compensate for the undocumented workspace parameter.

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?

The description names a specific resource (usage and savings stats) and enumerates the metrics it reports: local lookup time, estimated tokens/ms saved, hit rate, plus the scope (one workspace/repo or everything). It does not, however, distinguish itself from the sibling amem_usage_report, which sounds like it covers the same ground, so an agent cannot disambiguate the two from the text alone.

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

Usage Guidelines4/5

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

The triggers are stated concretely: 'Use when asked how much amem helped, how often it hit, or usage over time.' That gives a clear when-to-use context. It stops short of when-not-to-use or naming an alternative, and given the overlapping amem_usage_report sibling, that omission matters.

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