Skip to main content
Glama

Archive overview

archive_stats
Read-onlyIdempotent

Get an overview of the vulnerability archive: report counts, data freshness, severity mix, yearly volume, top bug classes, programs, researchers, and latest disclosures.

Instructions

Overview of the whole archive: how many reports, how fresh the data is, severity mix, reports per year, top bug classes, programs and researchers, and the latest disclosures.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description then adds real value by enumerating the aggregation content returned (counts, freshness, severity mix, per-year breakdown, top classifications, latest disclosures), which is the main thing an agent needs since there is no output schema.

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?

One sentence, front-loaded with the scope ('Overview of the whole archive') before the enumeration. The list is long but each item names a distinct aggregate an agent could care about, so it earns its space; a slightly tighter phrasing would be the only improvement.

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?

With no parameters, no output schema and annotation coverage of the safety profile, the description's enumeration of returned aggregates is the key missing piece and it supplies it. Freshness semantics and any cost/latency expectations for a whole-archive scan are the only notable omissions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 for a no-param tool applies at its highest. Nothing in the description misleads about inputs.

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 specific resource and scope: an aggregate 'overview of the whole archive' rather than a single report, which distinguishes it in spirit from get_report and search_reports. It stops short of naming a sibling explicitly, so differentiation is inferred from 'whole archive' rather than stated.

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

Usage Guidelines3/5

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

Usage is implied by the word 'overview' — an agent should reach for this when it wants aggregate figures instead of individual records — but there is no explicit when-to-use statement, no exclusion, and no mention of the sibling tools it substitutes for.

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