Skip to main content
Glama

Dragons Eye Ransomware Claims

cve_intel

Read-onlyIdempotent

Everything an agent needs to prioritize one CVE: CVSS, affected vendors/products, vendor advisories, CISA KEV status and known ransomware use, EPSS, recorded public exploit repositories, an AI-generated attack flow with ATT&CK technique ids (flagged as AI-generated) and suggested MITRE D3FEND countermeasures. CVEs not cached yet return an error (queued, not charged). The former free cve_status tool is retired and returns directions only; some former status-only CVEs have no paid detail. Costs $0.03 USDC per call via x402 (payment goes in _meta["x402/payment"]); invalid input or an upstream failure returns an error and is not charged.

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": {
      "id": "<id>"
    },
    "name": "cve_intel"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCVE id, e.g. CVE-2026-0257

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description layers on the material behavioral facts: cost of $0.03 USDC via x402, the exact _meta["x402/payment"] carrier, cache-miss behavior (error, queued, not charged), and the no-charge guarantee on invalid input or upstream failure. It also flags that the attack flow is AI-generated, which is an important trust signal not present in any structured field.

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 payoff list of data returned, then the caveats (cache miss, retired tool, pricing). It is dense and somewhat run-on across sentences, but nearly every clause carries actionable information for invocation and payment handling.

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

Completeness5/5

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

No output schema exists, and the description compensates by enumerating the returned intel categories and flagging the AI-generated portion. Combined with explicit failure/payment semantics, an agent has everything needed to invoke correctly and interpret the charge behavior.

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 sole parameter already carries a description, a regex pattern, and an example. The description adds no extra meaning about the id format or normalization, so the baseline 3 is appropriate for a fully documented single parameter.

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 and resource ('prioritize one CVE') and then enumerates the exact payload: CVSS, vendors/products, advisories, KEV, EPSS, exploit repos, ATT&CK-mapped attack flow, D3FEND countermeasures. The enumeration of returned fields makes it clearly distinguishable from siblings like cve_batch_intel and the retired cve_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent that the former cve_status tool is retired and returns directions only, and that some status-only CVEs have no paid detail — which steers the agent away from a stale alternative. It does not explicitly state the single-CVE vs cve_batch_intel split, so the batch alternative is only implied.

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