VoidMob MCP

Official

by voidmobcom

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Search eSIM plans

search_esim_plans

Read-onlyIdempotent

Find prepaid eSIM travel data plans by country or region; filter by data, days, 5G, hotspot, and price, with paged results via cursor.

Instructions

Search prepaid eSIM data plans for travel by country or region: data allowance, validity, price, 5G, hotspot, calls/SMS and top-up support. Results are paged - pass cursor for more. Next: show the user the plan and price, then purchase_esim with the prod_ id and that price as max_price_cents.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`query`	No	Substring search on plan title (e.g. 'Europe')
`cursor`	No
`has_5g`	No
`country`	No	ISO-3166 country code, any case (e.g. 'JP'): plans that cover this country
`min_days`	No
`has_hotspot`	No
`min_data_gb`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`esim_plans`	Yes
`next_cursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.2.1Oct 1, 2026

changedInput schema / properties / country / description

Previous value: -"ISO-3166 country code (e.g. 'JP')"New value: +"ISO-3166 country code, any case (e.g. 'JP'): plans that cover this country"

addedInput schema / properties / country / pattern
```
Added value: +"^[A-Za-z]{2}$"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "esim_plans": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "countries": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "country_count": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "currency": {
+            "const": "USD",
+            "type": "string"
+          },
+          "data_limit_gb": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "data_unlimited": {
+            "type": "boolean"
+          },
+          "features": {
+            "additionalProperties": {},
+            "properties": {
+              "has_5g": {
+                "type": "boolean"
+              },
+              "has_calls": {
+                "type": "boolean"
+              },
+              "has_hotspot": {
+                "type": "boolean"
+              },
+              "has_sms": {
+                "type": "boolean"
+              },
+              "supports_topup": {
+                "type": "boolean"
+              }
+            },
+            "required": [
+              "has_5g",
+              "has_hotspot",
+              "has_calls",
+              "has_sms",
+              "supports_topup"
+            ],
+            "type": "object"
+          },
+          "id": {
+            "type": "string"
+          },
+          "price_cents": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "region": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "routing_location": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "type": "string"
+          },
+          "validity_days": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "countries",
+          "region",
+          "country_count",
+          "routing_location",
+          "data_limit_gb",
+          "data_unlimited",
+          "validity_days",
+          "features",
+          "price_cents",
+          "currency"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "next_cursor": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "esim_plans",
+    "next_cursor"
+  ],
+  "type": "object"
+}

Changed6 schema fields changedv1.1.8Sep 30, 2026
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / min_data_gb / minimum
```
Added value: +0
```
- addedInput schema / properties / min_days / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / min_days / minimum
```
Added value: +0
```
- changedInput schema / properties / min_days / type
```
Previous value: -"number"New value: +"integer"
```
- changedInput schema / properties / query / description
```
Previous value: -"Substring search on plan title"New value: +"Substring search on plan title (e.g. 'Europe')"
```
First observedv1.1.3Aug 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely new behavior: results are paged and a cursor must be passed for more, plus the cross-tool handoff contract (prod_ id and max_price_cents). It does not describe result ordering or when paging ends.

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?

Two sentences, no filler, and the scoping facet list plus paging note are front-loaded before the next-step instruction. The facet enumeration is slightly dense but every clause carries information.

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?

With an output schema present, return values need not be explained, and the description covers filters, pagination and the follow-up purchase call. Minor gaps remain around the default/maximum limit and how cursor interacts with other filters.

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 description coverage is only 25% (query and country), leaving six undocumented params. The description compensates by naming the filterable facets that map to has_5g, has_hotspot, min_data_gb, min_days and country, and explains cursor usage. limit and its default/maximum remain unaddressed in prose.

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 ('Search prepaid eSIM data plans for travel') and enumerates the filterable facets (data allowance, validity, price, 5G, hotspot, calls/SMS, top-up). It is clearly distinguishable from sibling searches like search_sms_services, search_proxies and search_dedicated_countries.

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 an explicit downstream workflow ('show the user the plan and price, then purchase_esim with the prod_ id and that price as max_price_cents'), which tells the agent when this tool belongs in the purchase flow. It does not name exclusions or alternative search tools, so it stops short of a 5.

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