Skip to main content
Glama

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

One CVE checked against the ranked KEV set

check_cve
Read-only

One CVE checked against the ranked KEV set. One CVE checked against the Ni Biashara cybersecurity shelf's ranked snapshot: KEV status, EPSS, CVSS where pulled, ransomware flag, CISA's required action and due status — or an honest not-in-snapshot answer that never claims the CVE is unexploited. $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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cve": "<cve>"
    },
    "name": "check_cve"
  }
}

Input Schema

NameRequiredDescriptionDefault
cveYesCVE id, e.g. CVE-2026-109618 (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already cover read-only, open-world and non-destructive behavior. The description adds real value beyond that: the $0.1 USDC on Base price, the x402 402 → PAYMENT-SIGNATURE flow, and the important negative-result semantics ('honest not-in-snapshot answer that never claims the CVE is unexploited'). It does not address rate limits, caching or snapshot freshness/update cadence.

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

Conciseness3/5

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

The leading sentence is a verbatim copy of the title and earns nothing. The remaining text is dense and informative, but the payment mechanics sentence is long and underspecified in places (which URL, what the response body contains).

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?

For a one-parameter lookup with no output schema, the description covers the returned fields, the negative-result behavior and the payment handshake, which is most of what an agent needs. Missing snapshot freshness and any notion of alternative tools keeps it short of full completeness.

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?

There is one parameter with 100% schema description coverage, including a format example, so the schema carries this burden fully. The description adds no format, casing or normalization guidance beyond what the schema already states.

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 first sentence merely restates the title, but the second sentence names the resource and the concrete outputs: KEV status, EPSS, CVSS, ransomware flag, CISA required action and due status. That is specific enough to distinguish a single-CVE KEV lookup, though it never names how it differs from get_cve_plus or search_cyber_kev.

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 description implies the single-CVE lookup scenario and explains the two-step payment usage (call free, then pay on the returned URL), which is genuinely useful operating guidance. It gives no explicit when-to-use or when-not guidance relative to the obvious siblings, so routing still requires inference.

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