Skip to main content
Glama

Dragons Eye Ransomware Claims

coverage

Read-onlyIdempotent

Retired compatibility tool. Returns a retirement error and static directions to existing paid indicator_check, cve_intel and group_intel. These answer specific queries and do not replace the former coverage inventory.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, but they say nothing about the outcome of a call. The description adds the crucial behavior: the call fails with a retirement error and returns static directions rather than data. It does not state whether the error is raised or returned as content, which is the only remaining ambiguity.

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?

Three short sentences with the most important fact — 'Retired compatibility tool' — front-loaded. The closing clause about the alternatives not replacing the former inventory earns its place as a scope warning, though it is slightly indirect in phrasing.

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?

There is no output schema, so the description must explain what a call yields; it does so precisely (a retirement error plus static pointers to live tools). For a zero-parameter deprecated stub, nothing an agent needs before calling is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is empty at 100% coverage, so there is nothing for the description to clarify. Baseline for a parameterless tool applies, with no contradictory or missing parameter information.

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 description opens with a specific status and function: a retired compatibility tool that returns a retirement error. It explicitly names the live replacements (indicator_check, cve_intel, group_intel), so an agent can distinguish it from every sibling without opening a 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 signals when-not-to-use (the tool is retired) and names three alternatives, plus a caveat that those alternatives answer specific queries and do not reproduce the old coverage inventory. It stops short of routing among the three alternatives, but the exclusion guidance is explicit.

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