Skip to main content
Glama

Fetch a page over Tor

tor_fetch
Read-only

Download web pages, including .onion addresses, over Tor and return readable Markdown text with links, retrieval time, and a SHA-256 hash of the raw response.

Instructions

Download a web page (including .onion addresses) through Tor and return its readable text as Markdown plus its links. Fast and light: no JavaScript runs. Includes retrieval time and SHA-256 of the raw response. Use tor_browse for pages that need JavaScript or interaction.

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_fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the raw HTML/text instead of extracted Markdown
urlYeshttp(s) URL, e.g. https://www.torproject.org or an .onion address

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?

Annotations already mark the tool as read-only and open-world, and the description adds meaningful behavior beyond that: no JavaScript runs, the response includes retrieval time and SHA-256 of the raw response, and the output is Markdown plus links. These details help an agent understand what to expect from execution and results. No annotation contradiction is present.

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 three focused sentences with no wasted wording. Core scope and return behavior are front-loaded, followed by the routing advice for tor_browse. It is appropriately sized for a two-parameter fetch tool.

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?

Even though there is no output schema, the description explains the return format as readable Markdown plus links, with retrieval time and SHA-256 of the raw response. It also covers the key behavioral limitation, no JavaScript, and names the alternative for JavaScript-dependent pages. The definition is complete enough for an agent to call the tool correctly.

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?

Schema description coverage is 100%, so both the url and raw parameters are already documented in the schema. The description does not add extra parameter semantics beyond what the schema provides. The baseline of 3 is appropriate when the schema carries the parameter documentation.

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 states a specific verb and resource: download a web page through Tor, including .onion addresses, and return readable Markdown plus links. It clearly distinguishes this from tor_browse by noting that no JavaScript runs here. An agent can identify the tool's core function without opening the schema.

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?

It explicitly says to use tor_browse for pages that need JavaScript or interaction, which gives a concrete alternative and selection condition. The no-JavaScript limitation also implies when this tool is appropriate. Guidance is clear and actionable.

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