Skip to main content
Glama

Debian Security Advisories — buy per-query in-session (debianwatch)

data_preview

Read-onlyIdempotent

✅ No API key needed. Listing: Debian Security Advisories. Price 0.01 USDC/query (max 20 queries/session). Sample questions: What are the newest Debian security advisories?; List Debian advisories published in the last 72 hours. FREE preview — no key, no payment. Try one of the sample questions now.

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

Input Schema

NameRequiredDescriptionDefault
slugNoPublic listing slug. Defaults to the routed session's listing when connected via /mcp/data/{slug}/http.
questionNoOptional free-text question you'd ask this data (echoed back).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/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 adds genuinely useful operational facts – no API key needed and max 20 queries per session – but the pricing text ("0.01 USDC/query" alongside "FREE ... no payment") is muddled and could confuse an agent about cost.

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

Conciseness2/5

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

The text is marketing copy rather than documentation: the "no API key" claim appears twice, plus a price, a rate limit, two sample questions and a call-to-action. The core facts are buried and there is clear redundancy, though the opening line does front-load the free/keyless point.

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?

For a tool meant to be a free "taste" of a listing, the description never explains what the preview actually returns (the schema only hints at "public metadata only") or how it relates to the paid session tools. With 100% schema coverage and annotations, the remaining burden was to explain preview scope and next step, and it does not.

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 description coverage is 100%, so slug and question are already documented in the input schema, including the /mcp/data/{slug}/http routing default. The description adds nothing about either parameter, so the baseline 3 applies.

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 conveys that this is a free preview of a listing and names a concrete instance (Debian Security Advisories), but it never states plainly what the tool does at a general level or what a preview contains. An agent reading data_preview learns the flavor of the listing but not the verb/resource distinction from siblings such as data_session_query.

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?

There is an implicit invitation to call it ("Try one of the sample questions now") and a hint that it is free/no-key, but no explicit when-to-use, when-not-to-use, or routing to alternatives. Nothing says to use data_preview first and then data_session_query for full paid access.

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.

Resources