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

darknet-mcp-server

by badchars
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

tor_exit_check

Check if an IP address is a known Tor exit node using a cached list, helping identify traffic originating from the Tor network.

Instructions

Check if a specific IP address is a known Tor exit node. Uses cached exit node list.

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": {
      "ip": "<ip>"
    },
    "name": "tor_exit_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYesIP address to check

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?

The description discloses that the tool relies on a cached exit node list, which is a useful behavioral trait affecting data freshness. It does not mention output format, error behavior, or access requirements, but for a simple read-only check the cache note adds some value beyond the schema.

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 that immediately states the purpose and the cached data source, with no filler words or redundant information.

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?

The tool is simple (1 param), but there is no output schema or annotations. The description clarifies the purpose and data source but does not state what the response looks like. Given the simplicity, this is an acceptable but not complete description.

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 input schema already fully describes the 'ip' parameter, and the description adds little beyond restating 'specific IP address'. However, schema coverage is 100%, so the baseline of 3 applies.

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 the specific verb 'check' and clearly identifies the resource (a specific IP address) and the condition (known Tor exit node). This distinguishes it from sibling tools like tor_exit_nodes or tor_exit_details, which likely list or detail nodes.

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 use when an agent has a particular IP address to validate, but it does not explicitly contrast with sibling tools or state when not to use it. No alternatives are named, though the specificity of 'specific IP address' gives context.

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