Skip to main content
Glama
rushikeshmore

tor-mcp

by rushikeshmore
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

tor_privacy_status

Read-onlyIdempotent

Check your Tor connection status, exit IP, and routing configuration. Use for diagnostics to verify Tor connectivity and routing rules.

Instructions

Show current Tor connection status and routing configuration.

Provides a full health check: Tor connectivity, exit IP, control port availability, routing rules, and configuration. Use this for diagnostics.

Args: params (TorStatusInput): Validated input containing: - response_format (ResponseFormat): 'json' or 'markdown'

Returns: str: Complete privacy status.

JSON schema:
{
    "connection": {
        "connected": bool, "is_tor": bool, "exit_ip": str | null,
        "control_available": bool, "error": str | null
    },
    "routing": {
        "default_route": str, "user_tor_patterns": list,
        "user_direct_patterns": list, "use_defaults": bool
    },
    "config": {"socks_port": int, "control_port": int, "timeout": float},
    "health": str
}

Examples: - Use when: "Is Tor working?" -> default params - Use when: "Show me the routing config" -> default params - Use when: "Debug why requests are failing" -> default params - Don't use when: You just need to verify anonymity (use tor_check_anonymity)

Error Handling: - Returns status regardless of Tor state (offline status is valid)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is clear. Description adds value by stating 'Returns status regardless of Tor state (offline status is valid)', which is important behavioral context not in 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 (main, args, returns, json schema, examples, error handling). However, it is somewhat lengthy and could be more concise while retaining clarity.

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 presence of a detailed output schema and comprehensive annotations, the description covers all essential aspects: purpose, usage, parameters, return structure, error handling, and behavioral traits. 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 coverage is 0% but the description has an 'Args' section explaining the response_format parameter and its enum options (json/markdown). This adds meaning beyond the schema references. Could be more detailed on usage of each format.

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 'Show current Tor connection status and routing configuration' with specific verb and resource. Distinguished from siblings by naming tor_check_anonymity as the alternative for verifying anonymity.

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 usage examples for common queries (e.g., 'Is Tor working?', 'Show me the routing config', 'Debug why requests are failing') and a clear exclusion: 'Don't use when: You just need to verify anonymity (use tor_check_anonymity)'. Error handling note adds context.

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