VoidMob MCP

Official

by voidmobcom

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

List orders

list_orders

Read-onlyIdempotent

List SMS verifications, rentals, dedicated numbers, eSIMs, and proxies with status and price to recover orders whose purchase result was lost before rebuying.

Instructions

List your orders: SMS verifications (ver_...), long-term rentals (ren_...), dedicated numbers (ded_...), eSIMs (esim_...) and proxies (prx_...), with status and price. Without kind: the newest orders of every list. With kind: one page of that list, optionally filtered by status, with a cursor for the next page (only verifications are paged newest first). Use it to find an order whose purchase result was lost before buying again (e.g. kind='verification', status='waiting_for_code'), then the matching get tool for details. Statuses - verification: waiting_for_code/code_received/cancelled/expired; rental: active/expired/cancelled; dedicated: active/expired; esim: processing/completed/cancelled/refunded/expired; proxy: provisioning/active/expired/exhausted/refunded.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	No	One list to page through ('sms' = the first page of verifications and rentals)
`limit`	No	With kind: page size (default 20). Without kind: newest orders shown per kind (default 5)
`cursor`	No	With kind: next_cursor from the previous page of the same list
`status`	No	With kind: only orders in this status (see the description for each kind's statuses)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`orders`	Yes
`partial`	No
`next_cursor`	No
`incomplete_kinds`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv1.2.1Oct 1, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "With kind: next_cursor from the previous page of the same list",
+  "maxLength": 200,
+  "type": "string"
+}

changedInput schema / properties / kind / description

Previous value: -"Filter by kind (sms = verifications and long-term rentals)"New value: +"One list to page through ('sms' = the first page of verifications and rentals)"

changedInput schema / properties / kind / enum

Previous value: -[
-  "sms",
-  "esim",
-  "proxy",
-  "dedicated"
-]New value: +[
+  "verification",
+  "rental",
+  "dedicated",
+  "esim",
+  "proxy",
+  "sms"
+]

removedInput schema / properties / limit / default
```
Removed value: -20
```

addedInput schema / properties / limit / description

Added value: +"With kind: page size (default 20). Without kind: newest orders shown per kind (default 5)"

addedInput schema / properties / status

Added value: +{
+  "description": "With kind: only orders in this status (see the description for each kind's statuses)",
+  "maxLength": 40,
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "incomplete_kinds": {
+      "items": {
+        "enum": [
+          "verification",
+          "rental",
+          "dedicated",
+          "esim",
+          "proxy"
+        ],
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "next_cursor": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "orders": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "charged_price_cents": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "created_at": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "kind": {
+            "enum": [
+              "verification",
+              "rental",
+              "dedicated",
+              "esim",
+              "proxy"
+            ],
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          },
+          "summary": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "kind",
+          "id",
+          "status",
+          "charged_price_cents",
+          "created_at",
+          "summary"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "partial": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "orders"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedv1.1.8Sep 30, 2026

changedInput schema / properties / kind / description

Previous value: -"Filter by kind"New value: +"Filter by kind (sms = verifications and long-term rentals)"

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

First observedv1.1.3Aug 11, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so safety is covered. The description adds genuinely new behavior: paging semantics (newest-first only for verifications), the no-kind vs with-kind branching, and the full status vocabulary per kind. It omits auth requirements and rate limits, so not a full 5.

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?

Front-loaded with purpose and ID prefixes, then behavior, then usage, then statuses. Efficient for the amount of information conveyed, though the trailing status enumeration is long and slightly duplicates the kind/paging statements already given.

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, and the description covers kind branching, pagination, status filtering, and the routing to detail tools. Nothing an agent needs to call it 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% (baseline 3), but the description adds meaning beyond it: it explains the no-kind default ('newest orders of every list') and actually supplies the per-kind status enumerations that the schema's status field defers to. It also clarifies cursor paging only applies to verifications.

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?

Opens with a specific verb+resource ('List your orders') and immediately enumerates the five order kinds with their ID prefixes, which is far more precise than the sibling 'get_' tools. An agent can distinguish it from search_sms_services or list_proxy_lists 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?

Explicitly states the when: 'Use it to find an order whose purchase result was lost before buying again (e.g. kind=verification, status=waiting_for_code)', and routes to the alternative ('then the matching get tool for details'). This is a concrete decision rule, not an implied one.

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