Skip to main content
Glama

Open a page in the Tor browser

tor_browse

Opens any URL, including .onion sites, in headless Chromium routed through Tor and returns readable text and links for follow-up page interaction.

Instructions

Open a URL (including .onion) in a headless Chromium that routes all traffic through Tor, with a throwaway in-memory profile. Returns readable text and links. Use tor_click, tor_type and tor_screenshot afterwards. Set javascript=false for a safer, Tor-Browser-'Safest'-like mode.

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": {
      "url": "<url>"
    },
    "name": "tor_browse"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttp(s) URL or .onion address
javascriptNoRun page JavaScript (default true). false is safer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

The description adds highly valuable behavioral context beyond the annotations, specifically detailing that it uses a 'throwaway in-memory profile' and the specific runtime environment ('headless Chromium'). This is crucial operational knowledge for the AI agent.

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 highly dense and efficient, utilizing every clause to define the tool's mechanism, safety features, output type, and relationship to other available tools without being verbose.

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 complexity of running a headless browser via Tor, the definition is maximally complete, explaining the environment, the profile type, the output, and the proper workflow with related tools.

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?

While the schema provides types, the description adds necessary context to the 'javascript' parameter by explaining that setting it to false creates a 'safest' mode, which dictates the parameter's intended use case.

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 states the core function (Open a URL), the environment (headless Chromium), and the routing mechanism (all traffic through Tor), making it distinct from sibling interaction tools like tor_click or tor_type.

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

Usage Guidelines4/5

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

It provides clear guidance on sequencing by advising to use tor_click, tor_type, and tor_screenshot *after* browsing. It also provides a crucial 'when to use' scenario for the javascript parameter (when safety is preferred).

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