Skip to main content
Glama

Archive a page as evidence

tor_archive

Archive a web or .onion page for reporting by saving HTML, Markdown, a screenshot, and a manifest with UTC time, final URL, HTTP status, Tor exit IP, and SHA-256 hashes.

Instructions

Save a copy of a page for reporting: HTML, readable Markdown, a screenshot (browser mode) and manifest.json with UTC time, final URL, HTTP status, Tor exit IP and a SHA-256 for every file. Saved under ~/tor-mcp-archive (or TOR_MCP_ARCHIVE_DIR). This is the only tool that writes to disk.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tor_archive"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoURL to fetch and archive. Omit to archive the page currently open in tor_browse.
noteNoFree-text note stored in the manifest (e.g. why this was captured)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds substantial context beyond that — the exact artifact set, manifest contents (UTC time, final URL, HTTP status, Tor exit IP, per-file SHA-256), the save location and its TOR_MCP_ARCHIVE_DIR override, and the browser-mode dependency for screenshots. That is precisely the side-effect detail an agent needs before triggering a disk write.

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 sentences, no filler, with the deliverable list and the disk-write warning front-loaded. The parenthetical '(browser mode)' and the env-var override are compact qualifiers that earn their space.

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?

With no output schema, the description correctly takes on the burden of describing what gets written and where, which it does thoroughly. It omits what the tool returns to the caller (e.g., the archive path or confirmation) and any failure behavior for unreachable pages, leaving a small gap for a mutation tool.

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 coverage is 100%, so both parameters are already documented in the schema, including the 'omit to archive the open page' behavior for url. The description adds no extra syntax or meaning for note beyond the schema, so the baseline of 3 applies.

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 names a specific verb and resource ('Save a copy of a page') and enumerates exactly what is produced: HTML, Markdown, screenshot in browser mode, and manifest.json. It also differentiates itself from siblings with 'This is the only tool that writes to disk', so an agent can distinguish it from tor_screenshot and tor_fetch without opening any schema.

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 gives clear usage context ('for reporting') and a default invocation path ('Omit to archive the page currently open in tor_browse'), tying it to a sibling tool. It stops short of explicit when-not guidance, such as when to prefer tor_screenshot or tor_fetch instead, so it falls just below the top band.

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