VoidMob MCP

Official

by voidmobcom

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Account balance

get_account

Read-onlyIdempotent

Retrieve authenticated account ID, prepaid USD balance, rate limits, and spend limits to verify funds before purchase and confirm charges after uncertain results.

Instructions

Get the authenticated account: id, prepaid USD balance, and per-endpoint-group rate limits, plus any spend limits the owner set on this server. Use it before buying to confirm sufficient funds, and after an uncertain purchase result to see whether a charge landed. The balance is topped up with crypto in the dashboard by the account owner.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`account`	Yes
`owner_limits`	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": {
+    "account": {
+      "additionalProperties": {},
+      "properties": {
+        "balance": {
+          "additionalProperties": {},
+          "properties": {
+            "amount_cents": {
+              "maximum": 9007199254740991,
+              "minimum": -9007199254740991,
+              "type": "integer"
+            },
+            "currency": {
+              "const": "USD",
+              "type": "string"
+            },
+            "formatted": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "amount_cents",
+            "currency",
+            "formatted"
+          ],
+          "type": "object"
+        },
+        "created_at": {
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        },
+        "rate_limits": {
+          "additionalProperties": {
+            "additionalProperties": {},
+            "properties": {
+              "limit": {
+                "type": "number"
+              },
+              "window_seconds": {
+                "type": "number"
+              }
+            },
+            "required": [
+              "limit",
+              "window_seconds"
+            ],
+            "type": "object"
+          },
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        }
+      },
+      "required": [
+        "id",
+        "balance",
+        "rate_limits",
+        "created_at"
+      ],
+      "type": "object"
+    },
+    "owner_limits": {
+      "additionalProperties": {},
+      "properties": {
+        "budget_cents": {
+          "anyOf": [
+            {
+              "maximum": 9007199254740991,
+              "minimum": -9007199254740991,
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "budget_counted_cents": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "budget_remaining_cents": {
+          "anyOf": [
+            {
+              "maximum": 9007199254740991,
+              "minimum": -9007199254740991,
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "max_order_cents": {
+          "anyOf": [
+            {
+              "maximum": 9007199254740991,
+              "minimum": -9007199254740991,
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "read_only": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "read_only",
+        "max_order_cents",
+        "budget_cents",
+        "budget_counted_cents",
+        "budget_remaining_cents"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "account",
+    "owner_limits"
+  ],
+  "type": "object"
+}

First observedv1.1.3Aug 11, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful context beyond that: the balance model and the fact that top-up happens via crypto in the dashboard by the owner, meaning the agent cannot change funds through this tool. However it does not explain the shape or units of the rate-limit or spend-limit fields it advertises.

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?

Three sentences, front-loaded with what is returned and followed by usage triggers. Each sentence carries information, though the crypto top-up sentence is mildly tangential and could be folded into the behavioral note rather than standing as its own sentence.

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?

An output schema exists, so return-value documentation is not the description's burden. Coverage of purpose, usage triggers, and account/top-up context is sufficient for a parameterless read tool, and 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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. No parameter claims are made that could mislead.

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?

Specific verb (get) plus resource (authenticated account) and an explicit enumeration of returned fields: id, prepaid USD balance, per-endpoint-group rate limits, spend limits. This is clearly distinguished from siblings like get_rental, get_esim_status, or get_proxy_status, which return state about purchased resources rather than the account itself.

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 two concrete triggering conditions: before buying to confirm funds, and after an uncertain purchase result to check whether a charge landed. No alternatives or when-not conditions are named, but the conditions are specific enough that an agent can decide when to call it.

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