Skip to main content
Glama

New Tor identity

tor_new_identity

Rotate Tor circuits to get a new exit IP for new connections, then clear browser cookies, storage, and open pages to reset identity.

Instructions

Switch to new Tor circuits (new exit IP for new connections) and wipe the browser's cookies, storage and open page.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false; the description adds the important context that this mutates client state destructively, naming exactly what is wiped (cookies, storage, open page) and clarifying that the new exit IP applies only to new connections. It does not mention whether existing connections persist or how often identity changes are permitted.

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?

A single front-loaded sentence with two coordinated clauses: the primary effect first, the destructive side effect second. No filler and nothing restating the title verbatim.

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?

For a zero-parameter mutation tool with no output schema, the description covers the essential effects, including what state is destroyed. Minor omissions are frequency limits and whether the calling page is reloaded or left blank after the wipe.

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 for a no-parameter tool applies. Nothing in the description misrepresents the empty 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?

States a specific verb (switch) and resource (Tor circuits), plus the observable effect (new exit IP for new connections) and the side effect of clearing browser state. This clearly separates it from siblings like tor_status or tor_browse, which do not reset identity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the action itself, but there is no explicit when-to-use or when-not-to-use guidance, nor any warning about when resetting identity might be unwanted or rate-limited. An agent can infer the purpose but gets no routing cues.

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