Skip to main content
Glama
inbox-recall

inbox-recall

by joey12725

Archive overview

archive_stats
Read-only

Retrieve archive statistics such as connected networks, message counts, date coverage, and embedding coverage to assess stored chat data before searching or reconstructing threads.

Instructions

Networks, message counts, date coverage and embedding coverage of the archive.

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

Input Schema

NameRequiredDescriptionDefault
formatNotext: compact, citation-tagged transcript (default). json: the full structured result.text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the useful detail that results span multiple analytical dimensions (network, counts, coverage), but says nothing about cost, aggregation scope, or whether counts are exact.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, but it is a fragment rather than a sentence, and the listed dimensions are not prioritized or framed by purpose. Nothing is wasteful, yet nothing is maximally efficient either.

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

Completeness2/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 is the only place the agent can learn what a 'statistics' response actually contains, and it offers only a terse list. For a zero-parameter summary tool, it should state that it takes no input and give a clearer picture of return contents.

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 100% and the single format parameter is fully self-documented with default and enum semantics, so the baseline is 3. The description contributes nothing about output shape for the two formats, so no extra credit.

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?

The description is a noun phrase listing what the tool reports (networks, message counts, date coverage, embedding coverage) but never states a verb or that it's a read-only overview of the archive as a whole. An agent can guess it summarizes the archive, but the phrasing reads like a field list rather than a statement of function.

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?

No when-to-use guidance, no exclusions, and no routing to or from siblings like list_conversations or search_messages. The agent must infer that this is the 'what's in the archive at all' entry point versus the retrieval tools.

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