Skip to main content
Glama

Ni Biashara Shelves — Africa FX, freight & compliance checks (x402)

Exploited-vulnerability search — ranked KEV

search_cyber_kev
Read-only

Exploited-vulnerability search — ranked KEV. Filtered search over the Ni Biashara cybersecurity shelf's ranked CISA KEV set: known-exploited vulnerabilities joined with EPSS exploitation probability and triage-ranked. Filter by text, vendor, product, priority band, ransomware linkage or EPSS floor. $0.25 USDC on Base. Returns the x402 URL to GET (402 → PAYMENT-SIGNATURE → delivery). Free to call this tool; payment happens on the URL.

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

Input Schema

NameRequiredDescriptionDefault
qNofree text over vendor, product, vulnerability name and description (optional)
bandNopriority band: act_now, urgent or watch (optional)
limitNomax records to return (optional, default 25, max 60)
offsetNorecords to skip (optional, default 0)
vendorNovendor name text, e.g. PHP Group (optional)
productNoproduct name text, e.g. PHP (optional)
min_epssNoonly records with an EPSS score at or above this floor, 0 to 1 (optional)
ransomwareNotrue restricts to known-ransomware-linked records (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/destructive annotations, the description discloses the commercial and protocol behavior that materially changes how an agent must act: $0.25 USDC on Base, the tool itself is free to call, and it returns an x402 URL to GET following a 402 → PAYMENT-SIGNATURE → delivery handshake. That is real behavioral context an agent cannot get from annotations or 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?

Front-loaded with the purpose, then the data provenance, then facets, then the payment flow and return shape — a logical order with no filler. It is dense but each clause contributes; the only slight redundancy is restating the title verbatim at the start.

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 output schema, the description compensates by explaining that the return value is an x402 URL to GET and that payment occurs downstream, so an agent knows what it will receive. Pagination and limits are handled by the fully documented schema. Only a note on result ordering/ranking details is absent.

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 every one of the eight parameters is already documented with examples and ranges. The description only summarizes the filter facets ('text, vendor, product, priority band, ransomware linkage or EPSS floor') and omits limit/offset, adding marginal meaning beyond the schema. Baseline 3 applies.

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?

The description names a specific verb and resource ('filtered search over ... ranked CISA KEV set') and characterizes the underlying data precisely: known-exploited vulnerabilities joined with EPSS exploitation probability and triage-ranked. That level of specificity lets an agent distinguish this from adjacent cyber tools like check_cve or get_cve_plus without opening a schema.

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?

The facet list ('filter by text, vendor, product, priority band, ransomware linkage or EPSS floor') implies how to use it for narrowing a vulnerability list, but there is no explicit when-to-use vs. when-not guidance and no named alternative such as get_cyber_top_priority or check_cve. Usage is inferable rather than stated.

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