Skip to main content
Glama

tor_exit_check

Check whether an IP or domain resolves to a Tor exit node using the Tor Project's public bulk exit list, cached for 30 minutes.

Instructions

Check whether an IP (or a domain's IPs) is a Tor exit node.

Uses the Tor Project's public bulk exit list, cached for 30 minutes.

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

Input Schema

NameRequiredDescriptionDefault
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add genuinely useful behavior context – the Tor Project bulk exit list as source and a 30-minute cache, warning that results may be up to half an hour stale. However it does not state the response shape, rate limits, or what happens for a domain with many IPs.

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?

Two short sentences, front-loaded with the core action, second sentence adding only the source and cache detail an agent actually needs. No filler.

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 one-parameter lookup with no output schema, the definition covers what it checks, where the data comes from, and staleness. The main remaining gap is not saying what is returned (a boolean, or per-IP results for a domain), which matters given the domain branch.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% – the schema only says 'target: string' – so the description must compensate. It does, clarifying that target may be a bare IP or a domain, which is the key ambiguity for a single free-form string argument. It stops short of specifying accepted formats (CIDR? URL? IPv6?).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb and resource: 'Check whether an IP (or a domain's IPs) is a Tor exit node.' It also discloses the data source. It does not explicitly distinguish itself from sibling checks such as dnsbl_check, though the resource ('Tor exit node') is distinctive enough on its own.

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?

Usage is implied by the wording – an agent would infer this is for reputation/attribution checks on an address. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative check tool, so routing between this and dnsbl_check is left to inference.

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