VoidMob MCP

Official

by voidmobcom

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Re-rent an expired rental

re_rent_rental

Destructive

Re-rent an expired rental number for the same duration at your approved max price, if still available.

Instructions

Re-rent the same number for another period of its original duration, charged at re_rent_price_cents (shown by get_rental). Only works on an expired rental whose re_rent_available is true (the number has not been released yet). No duration argument. Requires max_price_cents: the re-rent price you showed the user and they approved; refused uncharged if the price is higher.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`rental_id`	Yes	ren_... id of an expired rental with re_rent_available=true
`max_price_cents`	Yes	The price you showed the user and they approved, in US cents (e.g. 250 = $2.50). Nothing is charged if the current price is higher; the new price comes back so you can ask the user again.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`rental`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.2.1Oct 1, 2026

addedInput schema / properties / max_price_cents

Added value: +{
+  "description": "The price you showed the user and they approved, in US cents (e.g. 250 = $2.50). Nothing is charged if the current price is higher; the new price comes back so you can ask the user again.",
+  "exclusiveMinimum": 0,
+  "maximum": 1000000,
+  "type": "integer"
+}

changedInput schema / required

Previous value: -[
-  "rental_id"
-]New value: +[
+  "rental_id",
+  "max_price_cents"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "rental": {
+      "additionalProperties": {},
+      "properties": {
+        "auto_renew": {
+          "type": "boolean"
+        },
+        "can_cancel": {
+          "type": "boolean"
+        },
+        "cancel_window_expires_at": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "charged_price_cents": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "country": {
+          "type": "string"
+        },
+        "created_at": {
+          "type": "string"
+        },
+        "display_id": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "duration": {
+          "type": "string"
+        },
+        "expires_at": {
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        },
+        "messages": {
+          "items": {
+            "additionalProperties": {},
+            "properties": {
+              "code": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "id": {
+                "type": "string"
+              },
+              "received_at": {
+                "type": "string"
+              },
+              "text": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "id",
+              "text",
+              "received_at"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "next_renewal_price_cents": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "paid_until": {
+          "type": "string"
+        },
+        "phone_number": {
+          "type": "string"
+        },
+        "re_rent_available": {
+          "type": "boolean"
+        },
+        "re_rent_blocked_at": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "re_rent_price_cents": {
+          "anyOf": [
+            {
+              "maximum": 9007199254740991,
+              "minimum": -9007199254740991,
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "refunded_cents": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "rental_type": {
+          "const": "rental",
+          "type": "string"
+        },
+        "service_id": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "service_name": {
+          "type": "string"
+        },
+        "status": {
+          "enum": [
+            "active",
+            "expired",
+            "cancelled"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "status",
+        "phone_number",
+        "service_id",
+        "service_name",
+        "country",
+        "duration",
+        "rental_type",
+        "charged_price_cents",
+        "auto_renew",
+        "next_renewal_price_cents",
+        "re_rent_available",
+        "re_rent_price_cents",
+        "re_rent_blocked_at",
+        "created_at",
+        "paid_until",
+        "expires_at",
+        "can_cancel"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "rental"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedv1.1.8Sep 30, 2026

changedInput schema / properties / rental_id / description

Previous value: -"ren_xxx from an expired LTR with re_rent_available=true"New value: +"ren_... id of an expired rental with re_rent_available=true"

addedInput schema / properties / rental_id / pattern
```
Added value: +"^(?:ren_[A-Za-z0-9_-]{1,64})$"
```

First observedv1.1.3Aug 11, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations declare destructive/openWorld/non-idempotent, and the description adds the operational semantics that matter most: it charges money, the charge is refused and nothing is billed if the current price exceeds max_price_cents, and the new price is returned so the user can be re-asked. That is exactly the behavioral detail annotations cannot convey.

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?

Four tight sentences, front-loaded with what the tool does, then eligibility, then the price-guard mechanic. Every clause carries information; nothing is padding.

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?

Eligibility conditions, the required approved-price parameter, failure semantics, and the fact that no duration is supplied are all covered; an output schema exists so return values need not be explained. Nothing an agent needs to invoke this 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?

Schema coverage is 100% and the schema descriptions already explain both rental_id (ren_... with re_rent_available=true) and max_price_cents (approved price, nothing charged if higher). The description largely restates this, so the baseline of 3 is appropriate.

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 (re-rent) on a specific resource (the same number) with a precise scope: another period of the original duration. This clearly separates it from rent_number, cancel_rental, and reuse_number without needing the 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 names the preconditions (expired rental, re_rent_available is true, number not yet released), states that no duration argument is taken, and gives the fallback behavior when the price check fails. An agent knows exactly when this applies and when it does not.

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