Retrieve current Tor exit node IP addresses from the official Tor Project bulk exit list to detect or verify Tor traffic.
Get a list of current Tor exit node IP addresses from the official Tor Project bulk exit list.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max IPs to return (default: all) |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true and openWorldHint=true, so safety and external-list behavior are covered. The description adds that the source is the official Tor Project bulk exit list, which gives useful provenance context, but doesn't mention update frequency, format, or pagination behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, tight sentence that front-loads the verb and resource with zero waste. Everything stated earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only list tool with annotations and full schema coverage, this is adequate but minimal. It doesn't help the agent choose between this and the several related Tor siblings, which is the main contextual gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the single optional limit parameter is well-documented in the schema. The description adds no additional parameter semantics, which is acceptable at this baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Get) and resource (list of Tor exit node IP addresses) with a clear source (official Tor Project bulk exit list). It distinguishes itself from the sibling tor_exit_check (which checks a specific IP) reasonably well, though it doesn't explicitly name that sibling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this versus tor_exit_check, tor_exit_details, or other Tor-related siblings. The agent must infer the difference between fetching a full list and checking/detailing a single node.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.