SoftGlaze Browser MCP

Overview Schema Source Related Servers Discussions Admin

Rotate a proxy's IP

rotate_proxy_ip

Requests a new proxy IP from the vendor via the saved rotation link or supported API, after user approval. Use when the current IP must change and rotation is supported.

Instructions

Asks the proxy vendor for a new IP using the rotation link saved on the proxy (or the vendor's API where SoftGlaze supports it). Only works where the vendor supports rotation. Asks the user first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "proxyId": "<proxyId>"
    },
    "name": "rotate_proxy_ip"
  }
}

Input Schema

Name	Required	Description	Default
`proxyId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, openWorldHint=true, non-idempotent, non-destructive). The description adds real context beyond that: the operation reaches an external vendor, depends on a saved rotation link per proxy, is capability-gated by vendor support, and will surface a user confirmation prompt — the last being a meaningful interaction trait not expressed 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?

Three short sentences, front-loaded with the action, then the mechanism, then the constraints. No filler, though the parenthetical about the vendor API could be folded more cleanly.

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 single-parameter action tool this covers the essentials: what it does, the capability gate, and the confirmation behavior. The remaining gap is outcome reporting — with no output schema, the description never says what the agent receives on success or what happens when rotation fails.

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?

One required parameter with 0% schema description coverage, so the description carries the burden but only implicitly — the saved rotation link is 'on the proxy,' which hints proxyId identifies that proxy, yet nothing states the expected identifier form or failure mode for an unsupported proxy.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Asks the proxy vendor for a new IP') and explains the mechanism (saved rotation link or vendor API). An agent can tell this mutates a proxy's IP rather than merely checking or assigning one, though it does not explicitly name a sibling like assign_proxy to contrast with.

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?

Gives two concrete preconditions: it only works where the vendor supports rotation, and it asks the user first before proceeding. What is missing is routing guidance — nothing says what to do when the vendor does not support rotation, nor which sibling to use instead.

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