Skip to main content
Glama

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

One CVE, fully enriched (premium)

get_cve_plus
Read-only

One CVE, fully enriched (premium). Premium: one CVE from the Ni Biashara cybersecurity shelf with its full enrichment view — CVSS, CWE list, EPSS with its as-of, vendor advisory, CISA required action and due status — with any missing enrichment layers named in the payload rather than padded. $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": "get_cve_plus"
  }
}

Input Schema

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

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?

With annotations only covering the safety profile (readOnly, openWorld, non-destructive), the description adds exactly the context that matters: missing enrichment layers are explicitly named in the payload rather than padded, the cost is $1 USDC on Base, calling the tool is free, and payment occurs on the returned x402 URL via the 402 → PAYMENT-SIGNATURE → delivery handshake. An agent knows the cost, the failure mode, and that the tool returns a URL rather than the data itself.

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 content is dense but mostly earns its place, and the price and delivery mechanics are front-loaded in the flow. The opening repeats the title almost verbatim ('One CVE, fully enriched (premium). Premium: one CVE...'), which is the one clearly redundant clause.

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 single-parameter tool with no output schema, the description covers the payload contents, the honesty behavior of the enrichment, the price, and the two-step delivery. Remaining gaps are minor: it does not say whether the returned x402 URL expires or how repeated lookups for the same CVE are billed.

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 'cve' parameter already carries its own format example (CVE-2026-109618) plus the required flag. The description adds no further meaning about the parameter (no normalization rules, no accepted variants), so the baseline of 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 verb and resource: fetch one CVE from the Ni Biashara cybersecurity shelf with a full enrichment view, and it enumerates the concrete layers (CVSS, CWE list, EPSS with as-of, vendor advisory, CISA required action/due status). That is far beyond restating the name. It only partially differentiates from the sibling check_cve — the 'premium' framing hints at a richer, paid variant, but the sibling is never named or contrasted.

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?

Usage is implied by the premium framing: use this when you need the full enrichment view for a single CVE. However, there is no explicit when-to-use/when-not statement and no named alternative such as check_cve for a free or basic lookup, so the agent must infer the routing from the word 'premium' alone.

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