Global Executables

Get dataset coverage

get_coverage

Read-onlyIdempotent

Check source-coverage metadata before interpreting a command miss to learn provenance, freshness, and negative-result limits, and whether absence is exhaustive or unknown.

Instructions

Explain snapshot provenance, source coverage, freshness, and negative-result limits.

    Call this with no parameters before interpreting a miss; use check_executable to look up a
    command, and do not use coverage metadata as an existence result. negative_lookup becomes
    exhaustive only when every declared source succeeded with exhaustive, unrestricted coverage;
    otherwise absence remains unknown. The tool reads fixed metadata without probing registries,
    and freshness may be unavailable because its partial scan is stored separately.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower, yet the description still adds real semantics: negative_lookup is exhaustive only if every declared source succeeded with exhaustive unrestricted coverage, absence otherwise remains unknown, and freshness may be unavailable because the partial scan is stored separately. That is substantive behavioral disclosure beyond the structured fields.

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?

Purpose is front-loaded in the first sentence, usage guidance follows, and no sentence is filler. The second sentence is clause-dense and jargon-heavy, which costs a little readability, but the information density is earned.

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?

An output schema exists, so return-value shape need not be restated; the description instead supplies the interpretive caveats an agent needs to read that output correctly (negative-result limits, registry non-probing, possibly-missing freshness). Nothing required to call or interpret the tool is missing.

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?

Zero parameters, so the baseline is 4. The description reinforces this with "Call this with no parameters," leaving no ambiguity about how to invoke it.

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 verb ("Explain") and enumerates the exact facets of the resource it returns: snapshot provenance, source coverage, freshness, and negative-result limits. It also implicitly separates itself from the executable-lookup siblings by routing command lookups to check_executable. The resource itself is somewhat abstract domain metadata, which keeps it just short of a crisp 5.

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?

Explicit when-to-use ("Call this with no parameters before interpreting a miss"), an explicit alternative ("use check_executable to look up a command"), and an explicit prohibition ("do not use coverage metadata as an existence result"). This is the full when/when-not/alternative triad.

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

Deploy Server