Skip to main content
Glama

Tor status

tor_status
Read-only

Starts Tor if needed and reports connection status, Tor version, and current exit IP as seen by websites so you can confirm traffic routes through Tor.

Instructions

Start Tor if needed and report whether it is connected, the Tor version and the current exit IP as seen by websites. Call this first to confirm traffic really goes through Tor.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses a real side effect (it may start Tor) and clarifies that the exit IP is externally observed rather than locally configured. It omits how long startup may take and what a failure looks like, which matters for a tool that can block on daemon startup.

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, front-loaded with the action and its outputs, then the usage rule. No filler or restatement of the title.

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 carries the burden of describing return values and does so concretely (connected status, version, exit IP). It is nearly complete for a zero-parameter diagnostic, missing only failure/timeout behavior.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline applies. The description correctly implies a no-argument call.

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?

States a specific action set (start Tor if needed) and the exact outputs (connection state, Tor version, exit IP as seen by websites). This clearly separates it from the browsing/fetching siblings, which act on content rather than reporting tunnel health.

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?

"Call this first to confirm traffic really goes through Tor" gives explicit ordering guidance relative to the other tor_* tools. It does not state when the tool is unnecessary or what to do if the check fails, so it stops short of full when/when-not coverage.

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