VoidMob MCP

Official

by voidmobcom

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Search proxy plans

search_proxies

Read-onlyIdempotent

Find mobile 4G/5G proxy plans by type, country, data allowance, and stock. Returns plan ID, location, duration, price, and availability for purchase.

Instructions

Search mobile (4G/5G) proxy plans. Shared plans are rotating mobile IPs billed by data; geo (country/region/city/ISP), sticky sessions and rotation are chosen after purchase per request or per list. Dedicated plans are one mobile modem of your own in a fixed country, carrier and region, with unmetered data and on-demand IP rotation. Each result shows the plan id, location, duration, price and (dedicated) stock. Without type, only shared plans are returned. Next: show the user the price, then purchase_proxy with the plan_ id and that price as max_price_cents.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	No	Plan kind. Omit for shared plans only.
`cursor`	No	With type set: the cursor from a previous search_proxies result, to fetch more plans
`country`	No	ISO-3166-1 alpha-2, any case (e.g. 'US'). Many shared plans are worldwide and match any country.
`min_data_gb`	No	Minimum included data allowance in GB (excludes dedicated plans)
`available_only`	No	With type set: only plans in stock right now

Output Schema

TableJSON Schema

Name	Required	Description	Default
`next_cursor`	Yes
`proxy_plans`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.2.1Oct 1, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "next_cursor": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "proxy_plans": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "available": {
+            "type": "boolean"
+          },
+          "carrier": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "country": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "country_name": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "data_gb": {
+            "anyOf": [
+              {
+                "maximum": 9007199254740991,
+                "minimum": -9007199254740991,
+                "type": "integer"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "duration_days": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "period": {
+            "enum": [
+              "daily",
+              "weekly",
+              "monthly"
+            ],
+            "type": "string"
+          },
+          "quoted_price_cents": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "region": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "type": {
+            "enum": [
+              "shared",
+              "dedicated_standard"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "type",
+          "country",
+          "data_gb",
+          "duration_days",
+          "quoted_price_cents"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "proxy_plans",
+    "next_cursor"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedv1.1.8Sep 30, 2026

changedInput schema / properties / country / description

Previous value: -"ISO-3166-1 alpha-2 (e.g. 'US'). Many shared plans are worldwide and match any country."New value: +"ISO-3166-1 alpha-2, any case (e.g. 'US'). Many shared plans are worldwide and match any country."

addedInput schema / properties / min_data_gb / minimum
```
Added value: +0
```

Changed5 schema fields changedv1.1.7Sep 27, 2026

addedInput schema / properties / available_only

Added value: +{
+  "description": "With type set: only plans in stock right now",
+  "type": "boolean"
+}

changedInput schema / properties / country / description

Previous value: -"ISO-3166-1 alpha-2 (e.g. 'US'). Many plans are worldwide and match any country."New value: +"ISO-3166-1 alpha-2 (e.g. 'US'). Many shared plans are worldwide and match any country."

addedInput schema / properties / cursor

Added value: +{
+  "description": "With type set: the cursor from a previous search_proxies result, to fetch more plans",
+  "type": "string"
+}

changedInput schema / properties / min_data_gb / description

Previous value: -"Minimum included data allowance in GB"New value: +"Minimum included data allowance in GB (excludes dedicated plans)"

addedInput schema / properties / type

Added value: +{
+  "description": "Plan kind. Omit for shared plans only.",
+  "enum": [
+    "shared",
+    "dedicated",
+    "all"
+  ],
+  "type": "string"
+}

First observedv1.1.3Aug 11, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations cover the safety profile (read-only, idempotent, closed-world), and the description adds substantial domain behavior beyond them: shared plans are billed by data, dedicated plans are a fixed-country modem with unmetered data, and each result carries plan id, location, duration, price and stock. This is context an agent cannot get from annotations or schema.

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?

It is dense but front-loaded: the purpose leads, plan-kind semantics follow, then the return fields and the mandated next action. Four sentences all carry weight, though the dedicated-plan detail could be tightened slightly without loss.

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 the description need not enumerate the return payload in full, yet it still summarizes the key fields and gives the agent an explicit follow-up action. Nothing needed to invoke or sequence this tool correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining what the two plan kinds actually represent and what omitting type does, plus how the returned plan_ id feeds the purchase step. It stops short of detailing cursor or available_only semantics, which the schema carries.

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 first sentence names a specific verb and resource ('Search mobile (4G/5G) proxy plans') and then splits the domain into shared vs dedicated with concrete characteristics of each. An agent can distinguish this from siblings like search_dedicated_countries, search_esim_plans, and search_sms_services 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 Guidelines5/5

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

It states the default behavior ('Without type, only shared plans are returned') and, critically, the next step: show the user the price, then call purchase_proxy with the plan_ id and that price as max_price_cents. It also explains that rotation/sticky/geo choices happen after purchase, which frames when to search vs when to purchase.

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