darknet-mcp-server

otx_search_pulses

Search for threat pulses using keywords and retrieve associated tags, malware families, and IOC counts.

Instructions

Search AlienVault OTX threat pulses by keyword. Returns matching pulses with tags, malware families, and IOC counts.

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": {
      "query": "<query>"
    },
    "name": "otx_search_pulses"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Search query
`limit`	No	Max results (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses what the operation returns ('matching pulses with tags, malware families, and IOC counts'), adding useful context beyond the schema. It does not mention authentication, rate limits, or pagination details, but for a simple search tool the behavioral traits are sufficiently transparent.

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 sentence, front-loaded with the purpose ('Search AlienVault OTX threat pulses by keyword') and followed by return-value details. No wasted words.

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

Completeness4/5

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

Given the simple interface (2 params, no output schema, no annotations), the description adequately covers the core behavior and return contents. It could mention pagination or default limit behavior, but those are already in the schema, so the description is nearly complete.

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%; both 'query' and 'limit' have clear descriptions in the schema. The tool description adds no additional parameter-level meaning, so the baseline score of 3 is appropriate.

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 uses a specific verb ('Search'), names the exact resource ('AlienVault OTX threat pulses'), and specifies the scope ('by keyword'). This clearly distinguishes it from sibling tools that target specific IOC types (otx_ip, otx_domain, otx_hash, otx_cve).

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?

The phrase 'by keyword' clearly implies this is the text-search tool, distinct from IOC-specific lookups among the siblings. However, it does not explicitly name alternatives or provide when-not-to-use guidance, so it stops short of a 5.

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

Deploy Server