Skip to main content
Glama
Sign In
mcp-stealth-browser

mcp-stealth-browser

by AntonLi-PM
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rotate_proxy

Force an immediate rotation to a new residential IP for a session to bypass IP blocks or rate limits.

Instructions

Force an immediate lease rotation to a new residential IP for the specified session.

Args: session_id: Session identifier to renew.

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": "rotate_proxy"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idNodefault

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

The description discloses that the tool forces an immediate lease rotation, which implies a side effect on the proxy IP. However, it does not mention potential consequences, rate limits, or whether the operation is synchronous or asynchronous, so behavioral transparency is partial.

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?

The description is concise and well-structured, using a single clear sentence for the tool purpose and a short, focused argument description. No unnecessary words or redundant information are present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the core action and parameter, but it does not mention return values, error conditions, or any output schema details. Given that an output schema exists, some additional context about expected results would improve completeness.

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?

The only parameter, session_id, is described as 'Session identifier to renew,' which clarifies its purpose. However, the description does not elaborate on whether it is required, how it is validated, or what happens if it is missing or invalid.

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's action: forcing an immediate lease rotation to a new residential IP for a specified session. This is specific and unambiguous, and it distinguishes the tool from the sibling tools that fetch, search, or check proxy status.

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

Usage Guidelines2/5

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

The description does not provide guidance on when to use this tool versus alternatives like proxy_status or stealth_fetch. It only states what the tool does, leaving the agent to infer appropriate usage context.

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

Deploy Server

Other Tools