Genexxis paid agent tools (x402)

cve_cve

CVE lookup by id or NVD keyword search (severity, days, maxItems): CVSS v3.1/v4 score+vector, CWE, affected products, references, CISA KEV status, EPSS score and a patch priority line. Price: $0.005 USDC per call, paid with x402 on Base.

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

Input Schema

Name	Required	Description
`id`	No	Exact CVE id, e.g. CVE-2021-44228 (alias: cve_id)
`days`	No	Only CVEs published within the last N days (1-120)
`keyword`	No	Free-text NVD keyword search (all words must match)
`maxItems`	No	Max results, default 20, max 50 (newest first)
`severity`	No	CVSS v3 severity filter

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden; it usefully discloses the paid x402/Base billing model and per-call price, which is critical pre-invocation context. It omits error behavior for unknown ids, rate limits, and whether results are cached or live NVD data.

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?

Two dense sentences: mode and capability envelope first, return fields next, pricing last. The parenthetical '(severity, days, maxItems)' is slightly redundant with the schema but does not bloat an otherwise tight definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Return content is adequately previewed and pricing covered, but with no output schema and no annotations, an agent still lacks guidance on mode conflicts, empty/error results, and how to route between this and its two CVE siblings.

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% with well-documented ranges (days 1-120, maxItems default 20 max 50, newest first), so the schema does the heavy lifting. The description only echoes parameter names as a parenthetical and adds no syntax or interaction detail, which is the expected baseline.

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?

States a specific verb+resource (CVE lookup) and enumerates both modes: exact id lookup or NVD keyword search with severity/days/maxItems filters. It also lists the returned fields (CVSS vectors, CWE, KEV, EPSS, patch priority), making scope unambiguous against siblings like cve_kev and cve_packages.

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?

The phrase 'by id or NVD keyword search' implies mode selection but never says when to pick this over cve_kev or cve_packages, or what happens when both id and keyword are supplied. No prerequisites or exclusions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Genexxis paid agent tools (x402) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?