Skip to main content
Glama

Dragons Eye Ransomware Claims

cve_status

Read-onlyIdempotent

Retired compatibility tool. Returns a retirement error and static directions to existing paid cve_intel; no CVE status or availability data. Paid detail does not replace every former status-only result.

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_status"
  }
}

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 declare readOnly/idempotent/non-destructive/closed-world, and the description adds the behavior that actually matters: the call always returns a retirement error and static text, never real data. That tells the agent the invocation is futile before it wastes a call, which is exactly the value-add expected beyond annotations.

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?

Retirement status is front-loaded in three short sentences with no padding. The final sentence ('Paid detail does not replace every former status-only result') is somewhat vague and could be read as implying partial usefulness, which slightly muddies an otherwise crisp message.

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?

For a one-parameter tool that only emits an error, the description covers everything an agent needs: retired status, what is returned, where to go instead, and a caveat about coverage gaps. No output schema is needed since the return is described as a fixed retirement error.

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 description coverage is 100% — the single id parameter has a regex pattern and a concrete example — so the schema fully carries parameter meaning. The description adds no additional semantics about the id (e.g., that it is only echoed back in the error), so the baseline of 3 applies.

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?

The first sentence labels the tool precisely ('Retired compatibility tool'), and the second states exactly what a call yields: a retirement error plus static directions to cve_intel, with no CVE status data. It explicitly distinguishes itself from the sibling cve_intel, so an agent can route without opening either schema.

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?

It clearly redirects the agent to the paid cve_intel alternative, which is the actionable when-to-use guidance. It stops short of stating an explicit 'never call this' or describing the legacy-client conditions under which a call is still meaningful, and the trailing caveat about coverage is not framed as a usage rule.

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