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

darknet-mcp-server

by badchars
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

tor_search_onion

Search the Tor network for .onion hidden services using Ahmia.fi. Returns matching site titles, URLs, and descriptions.

Instructions

Search for .onion sites using Ahmia.fi search engine. Returns titles, URLs, and descriptions of matching hidden services.

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

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query
limitNoMax results (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/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 that the tool searches an external engine (Ahmia.fi) and returns specific result fields, but does not mention potential limitations, rate limits, network requirements, or behavior on failed searches.

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, focused sentence that front-loads the core action and result. Every word contributes to understanding, with no redundant or filler content.

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?

For a simple search tool with two parameters and no output schema, the description adequately covers the return shape and purpose. It could mention default limit behavior, but the schema covers that. Overall sufficiently complete for its complexity.

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% for both parameters (query and limit), so the description adds little beyond what the schema already provides. The description confirms the overall purpose but does not enrich parameter meaning significantly.

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 specifies the action ('Search for .onion sites') and the resource/engine ('using Ahmia.fi search engine'), and distinguishes itself from sibling tools like tor_fetch_onion or tor_scrape_onion by stating it returns search result listings (titles, URLs, descriptions).

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?

It implies usage for searching .onion sites via Ahmia.fi, but does not explicitly state when to prefer this over alternatives or provide exclusions/edge cases. The description gives a clear context but no comparative guidance against siblings.

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