Skip to main content
Glama
badchars

darknet-mcp-server

by badchars

threatfoxTag

Search ThreatFox IOCs by tag (e.g., Cobalt Strike, Emotet). Returns up to 1000 results.

Instructions

Search ThreatFox IOCs by tag (e.g., "Cobalt Strike", "Emotet", "AgentTesla").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagYesTag to search for (e.g., Cobalt Strike, Emotet)
limitNoMax results to return (1-1000, default 100)
Behavior2/5

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

No annotations provided, so the description must disclose behavior. It only says 'Search ... by tag' without mentioning that it is read-only, what the response format is, or any side effects. For a simple search tool, this is minimal.

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?

Single sentence, front-loaded with verb and examples. No unnecessary words.

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?

With 2 simple parameters and no output schema, the description is adequate but omits details like result format. It is minimally complete for a basic search tool.

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%, baseline 3. The description adds example values for 'tag' but no additional meaning for 'limit'. It does not significantly enhance parameter understanding 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 the tool searches ThreatFox IOCs by tag, with concrete examples. It is specific and distinguishes from siblings like threatfoxSearch or bazaarTag.

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 when to use (when searching by tag) but does not explicitly mention when not to use it or suggest alternative tools for other search criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/badchars/darknet-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server