Skip to main content
Glama

index_stats

Read-only

Report on the local catalog index, if one has been built or fetched.

Lets a long-running agent decide whether searches will be instant (index
present) or pay a live S3 walk, and how stale the snapshot is. ``end`` is
the newest acquisition that is not ``datetime_suspect``.
``datetime_suspect_count`` is how many kept rows carry that flag.
``quarantined_future_count`` is how many source rows the last build
dropped for a datetime more than a day ahead (they are not in the index).
``unique_captures`` is how many rows are the canonical copy of their
collect; it equals ``items`` until republished copies have been linked.
``path`` is the index file locally and ``null`` on the public host, which
does not reveal the server filesystem.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, and the description adds real context beyond it: it discloses that the index may be absent (triggering a live S3 walk), explains staleness via 'end', and notes that the public host returns null for 'path' to avoid revealing the server filesystem. That filesystem-exposure note is useful behavioral detail the annotations cannot express.

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?

The opening sentence is well front-loaded, but the bulk is a field-by-field glossary (end, datetime_suspect_count, quarantined_future_count, unique_captures, path) that largely restates an output schema that already exists. The information is accurate but verbose for what it adds.

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

Completeness4/5

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

For a zero-parameter, read-only introspection tool with an output schema, the definition is thorough: it explains index presence, staleness, flagged rows, and host-specific path behavior. It stops short of stating the return shape when no index exists, only implying it via 'if one has been built'.

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 no parameters, so there is nothing to disambiguate; baseline is 4. The description uses the space instead to define return-field semantics rather than input meaning.

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?

States a concrete verb and resource: 'Report on the local catalog index'. The conditional 'if one has been built or fetched' clarifies scope. It does not explicitly distinguish itself from stack_stats or search_catalog, so it falls short of a 5.

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?

Gives a clear decision context: a long-running agent uses it to learn whether searches will be instant (index present) or will pay a live S3 walk, and how stale the snapshot is. That is a genuine when-to-use signal, though no explicit when-not or named alternative (e.g., search_catalog) is given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.