Skip to main content
Glama

tor_new_identity

Request a new Tor circuit to get a different exit IP, changing your apparent location. Verifies IP change and handles rate-limiting automatically.

Instructions

Request a new Tor circuit to get a different exit IP.

Changes your apparent location and IP address by requesting a new circuit from the Tor daemon. Requires the Tor control port (9051). Rate-limited to once per 10 seconds by Tor itself.

Args: params (TorCircuitInput): Validated input containing: - verify (bool): Check if IP actually changed (default: True) - response_format (ResponseFormat): 'json' or 'markdown'

Returns: str: Circuit rotation result.

JSON schema:
{
    "success": bool,
    "old_ip": str | null,
    "new_ip": str | null,
    "ip_changed": bool | null,
    "waited_seconds": float  (only if rate-limited)
}

Examples: - Use when: "Get a new exit IP" -> default params - Use when: "A site rate-limited me" -> default params - Use when: "I need to appear from a different location" -> default params - Don't use when: You just need to check current IP (use tor_check_anonymity)

Error Handling: - stem not installed: Returns pip install instruction - Control port not enabled: Returns torrc configuration hint - Rate-limited: Waits automatically (max 10s), reports wait time

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Discloses that it changes IP, requires Tor control port 9051, is rate-limited to once per 10 seconds, and details error handling (stem not installed, control port not enabled, rate limiting). This goes beyond the annotations (readOnlyHint=false, etc.).

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?

Well-structured with clear sections and front-loaded purpose. Every sentence adds value, though there is slight repetition in the examples (e.g., 'default params' repeated).

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?

Covers prerequisites, rate limiting, error handling, return schema, and example usage. No gaps given the tool's complexity and the presence of an output schema.

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 description lists the fields of the params object with defaults and meanings, but the input schema already provides descriptions for each parameter. The description adds value through usage examples and error handling context, but the parameter details are largely redundant with the schema.

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 tool requests a new Tor circuit to get a different exit IP, and distinguishes it from sibling tools by explicitly noting not to use for checking IP (use tor_check_anonymity instead).

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?

Provides explicit examples of when to use (e.g., 'Get a new exit IP', 'A site rate-limited me') and when not to use ('You just need to check current IP'), including a sibling tool alternative.

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