Skip to main content
Glama

Data coverage and freshness

registry_stats
Read-onlyIdempotent

Report the coverage and freshness of the BORME data behind this server.

Use it to answer "how much data is there?", "how fresh is it?" and "can I trust date filters for period X?" before running searches; it says nothing about any one company.

Returns JSON {events_approx, companies_approx, coverage: {from, to}, parse_completeness_last_30d, source}: exact event and company counts from the latest hourly snapshot (planner estimates if no snapshot exists), the first and latest publication day held (YYYY-MM-DD), and the event-weighted parse completeness over the 30 days up to the latest run (e.g. 0.9987). Takes no arguments. Read-only, open to everyone, no key needed and not counted against a quota. The same report is the resource borme://coverage.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds genuinely new context: no arguments, open access with no API key, not counted against a quota, counts come from the latest hourly snapshot with planner estimates as a fallback, and completeness is event-weighted over a rolling 30 days.

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?

Front-loaded with purpose, then usage, then return shape — all content-bearing. The return-value sentence is long and packs several fields into one breath, which slightly hurts scanability but is justified because there is no output schema.

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?

Because no output schema exists, the description carries the full burden of documenting the response and does so field by field (events_approx, companies_approx, coverage from/to, parse_completeness_last_30d, source) with formats and fallback behavior. An agent can call and interpret it without further information.

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?

With zero parameters the baseline is 4, and the description confirms "Takes no arguments," which is the only parameter semantics available here. Nothing further can be added.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Report the coverage and freshness of the BORME data") and immediately scopes it as server-wide metadata that "says nothing about any one company," which cleanly separates it from search_companies/search_events/company_history siblings.

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

Usage Guidelines5/5

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

Explicitly says when to use it ("before running searches") with the concrete questions it answers ("how much data is there?", "can I trust date filters for period X?"), and points to the equivalent alternative (the borme://coverage resource). No inference required.

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.