Skip to main content
Glama

tor_private_fetch

Read-onlyIdempotent

Privately fetch web pages via Tor, automatically deciding Tor or direct routing based on URL patterns for .onion, OSINT, and Tor-blocking sites.

Instructions

Fetch a URL with privacy-aware routing through Tor.

Automatically decides whether to route through Tor or direct based on URL pattern matching. Built-in rules route .onion through Tor, localhost direct, OSINT domains (Shodan, HIBP) through Tor, and Tor-blocking domains (GitHub, OpenAI) direct.

Args: params (TorFetchInput): Validated input parameters containing: - url (str): Target URL (e.g., 'https://example.com') - method (str): HTTP method, default GET - force_tor (bool): Override routing rules, force Tor - force_direct (bool): Override routing rules, force direct - response_format (ResponseFormat): 'json' or 'markdown'

Returns: str: Response with status_code, content, routing decision, and content_type.

JSON schema:
{
    "status_code": int,
    "url": str,
    "content_type": str,
    "content": str,
    "routed_through": "tor" | "direct",
    "routing": {"route": str, "reason": str}
}

Examples: - Use when: "Fetch this webpage anonymously" -> url="https://example.com" - Use when: "Check Shodan for host info" -> url="https://api.shodan.io/..." - Use when: "Access onion site" -> url="http://xyz.onion/page" - Don't use when: You need to verify Tor is working (use tor_check_anonymity) - Don't use when: You need a new exit IP first (use tor_new_identity)

Error Handling: - Connection refused: Tor not running, returns install instructions - 403 Forbidden: Target blocks Tor, suggests force_direct or new_identity - 429 Rate Limited: Suggests tor_new_identity for fresh exit IP - Timeout: Suggests increasing TOR_TIMEOUT

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. Description adds substantial behavioral context: automatic routing rules, error handling for various HTTP responses, and response format details. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is well-structured with sections (Args, Returns, Examples, Error Handling). It is front-loaded with the core purpose. While somewhat lengthy, all content is relevant and earns its place. A minor trim could be possible, but overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (automatic routing, error handling, multiple use cases), the description is remarkably complete. It covers the routing decision logic, error scenarios with suggested actions, and provides a detailed output schema. No gaps identified.

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 descriptions already cover parameter meanings, but description adds valuable context beyond schema: explains automatic routing logic, when to use force_tor/force_direct, and error handling strategies that relate to parameters. Since schema coverage is high, baseline is 3, and description adds enough to warrant a 4.

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?

Description clearly states it fetches a URL with privacy-aware routing through Tor. Uses specific verb 'fetch' and resource 'URL', and distinguishes from sibling tools like tor_check_anonymity and tor_new_identity in usage guidelines.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'Use when' and 'Don't use when' examples with clear alternatives, e.g., 'Don't use when: You need to verify Tor is working (use tor_check_anonymity)'. Provides excellent context for when to use this tool versus siblings.

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/rushikeshmore/tor-mcp'

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