Skip to main content
Glama
voidmobcom

VoidMob MCP

Official
by voidmobcom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Rotate dedicated proxy IP

rotate_proxy_ip
Destructive

Force a new exit IP on a dedicated proxy when open connections drop; applies a 60-second cooldown per proxy.

Instructions

Force a new exit IP on a dedicated proxy; open connections drop. 60-second cooldown per proxy. Shared proxies rotate per request instead (list settings or gateway username parameters).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
proxy_idYesprx_... id of a dedicated proxy

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
proxy_idYes
current_ipYes
rotated_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "current_ip": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "proxy_id": {
+      "type": "string"
+    },
+    "rotated_at": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "proxy_id",
+    "rotated_at",
+    "current_ip"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changedv1.1.8
    • addedInput schema / properties / proxy_id / description
      Added value: +"prx_... id of a dedicated proxy"
    • addedInput schema / properties / proxy_id / pattern
      Added value: +"^(?:prx_[A-Za-z0-9_-]{1,64}|PRX[A-Za-z0-9]{1,32})$"
  3. First observedv1.1.3

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructive=true and non-idempotent, so the bar is lower, yet the description adds real value beyond them: the consequence ('open connections drop') and a rate limit ('60-second cooldown per proxy'). These are the exact traits an agent needs to sequence calls safely.

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?

Three tight clauses lead with the action and scope, then the side effect, then the rate limit, and finally the alternative. Every sentence earns its place with no redundancy.

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?

With an output schema present, return values need no explanation; the description covers the action, its destructive side effect, the cooldown constraint, and the differing behavior of shared proxies. Nothing an agent needs to invoke it correctly is missing.

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?

There is a single proxy_id parameter with 100% schema description coverage, so the schema fully documents it. The description adds no syntax or format detail beyond what the schema provides, making this a baseline 3.

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 and resource ('Force a new exit IP on a dedicated proxy') and explicitly contrasts with the sibling behavior ('Shared proxies rotate per request instead'), letting an agent distinguish rotate from other proxy tools without opening a schema.

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 clear context for use (dedicated proxy) and points to the alternative mechanism for shared proxies via 'list settings or gateway username parameters.' It stops short of naming a specific sibling tool to call, but the when-to-use boundary is well drawn.

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