Skip to main content
Glama
Sign In
darknet-mcp-server

darknet-mcp-server

by badchars
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ransomwareByCountry

Retrieve ransomware victims filtered by country using ISO 3166-1 alpha-2 codes.

Instructions

Get ransomware victims filtered by country using ISO 3166-1 alpha-2 country code. Example codes: US, GB, DE, TR, FR, JP.

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": {
      "countryCode": "<countryCode>"
    },
    "name": "ransomwareByCountry"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryCodeYesISO 3166-1 alpha-2 country code (e.g. 'US', 'GB', 'DE', 'TR')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states the core behavior but does not disclose response format, pagination, or limitations, although this is a simple read operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with useful examples, no redundant content, and front-loaded action.

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?

For a one-parameter tool with no output schema, the description provides the essential purpose but lacks details on return value structure or limits, leaving some ambiguity.

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?

The schema already provides full parameter coverage with a description of the countryCode parameter including examples. The description repeats similar examples and the ISO standard, adding minimal new information beyond the schema.

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 clearly states 'Get ransomware victims filtered by country' with a specific filter and example codes, distinguishing it from sibling tools like ransomwareBySector or ransomwareSearch.

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?

The description implies usage for country-based lookups but does not explicitly mention when to use this tool over alternatives or provide exclusion criteria. It lacks guidance on alternatives.

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

Deploy Server

Other Tools