Skip to main content
Glama

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

Top-priority patch list — ranked KEV

get_cyber_top_priority
Read-only

Top-priority patch list — ranked KEV. The patch-this-first answer from the Ni Biashara cybersecurity shelf: the highest-ranked known-exploited vulnerabilities right now, ordered by priority score (EPSS plus ransomware linkage), with the full band counts of the ranked set. $0.1 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": "get_cyber_top_priority"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNohow many records to return, max 25 (optional, default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly, openWorld, non-destructive); the description goes well beyond by disclosing the price ($0.1 USDC on Base), the exact x402 handshake (402 → PAYMENT-SIGNATURE → delivery), and the crucial fact that the tool returns a URL to GET rather than the data itself. It also clarifies that calling the tool is free and payment occurs on the returned URL, which prevents a costly misassumption.

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?

The purpose is front-loaded in the first sentence, and the payment mechanics follow in a tight sequence. Every sentence is load-bearing, though the x402 arrow notation and 'Ni Biashara cybersecurity shelf' branding add mild density without much decision value.

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 does the work of explaining that the return is a payable URL plus how to redeem it, and it notes the payload includes band counts of the ranked set. It is close to complete for a one-parameter tool; only the exact response shape beyond 'band counts' remains unstated.

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 coverage is 100% and the single 'limit' parameter is fully documented in the schema (max 25, default 10). The description adds nothing about it, but with one fully-described optional parameter the schema carries the burden adequately, so baseline 3 applies.

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 states a specific resource ('highest-ranked known-exploited vulnerabilities right now') and the ordering logic ('priority score (EPSS plus ransomware linkage)'), which is far more than a restatement of the name. It implicitly separates itself from a plain search by emphasizing 'ranked' and 'top-priority,' but it never names search_cyber_kev as the contrast, so sibling differentiation is inferred 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?

'The patch-this-first answer' signals the intended use case — an agent wanting a prioritized remediation list rather than raw CVE lookup. However, there is no explicit when-not-to-use guidance and no named alternative for the search/filter case, leaving the agent to infer that search_cyber_kev covers exploratory queries.

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