Skip to main content
Glama
Sign In
VoidMob MCP

VoidMob MCP

Official
by voidmobcom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Deposit status and coins

get_deposit
Read-onlyIdempotent

Retrieve deposit status and payment instructions by ID, or list supported coins and recent deposits to reuse an open one.

Instructions

With deposit_id: one deposit's status (awaiting_payment, confirming, underpaid, credited, expired), where and how much to pay, how much more to send to complete an underpaid deposit, and what was credited. Without it: the coins you can deposit with their minimum and maximum, and the 5 newest deposits, so an open one can be reused instead of creating another.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_deposit"
  }
}

Input Schema

NameRequiredDescriptionDefault
deposit_idNoA dep_... id; leave out to list the coins and the newest deposits

Output Schema

NameRequiredDescriptionDefault
coinsNo
depositNo
depositsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds genuinely new behavior: which status values can come back, that an underpaid deposit reports the additional amount still owed, and that the no-id mode returns only the 5 newest deposits — a bounded-result detail not present in any structured field.

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, front-loaded with the branch condition 'With deposit_id' before the alternative, so the agent hits the decision point first. The status enumeration and return-value list make the sentence dense, but no clause is filler; slight tightening would still help readability.

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, yet the description still summarizes what each mode yields, which is more than required. For a single optional-parameter, read-only lookup, everything an agent needs to choose a mode and interpret the result is present.

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% and the pattern is documented, so the baseline is 3. The description goes beyond the schema by explaining the semantic consequence of omitting deposit_id (coins plus recent deposits) rather than merely restating the parameter, which materially changes how an agent should call it.

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 description splits the tool into its two concrete modes: with deposit_id it returns one deposit's status, payment target, shortfall and credited amount; without it, it returns depositable coins and the 5 newest deposits. The status vocabulary (awaiting_payment, confirming, underpaid, credited, expired) makes the resource and its states unambiguous, and an agent can distinguish it from create_deposit purely from this text.

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?

Usage is clearly implied by the two-mode framing, and the phrase 'so an open one can be reused instead of creating another' actively steers the agent away from create_deposit when a deposit already exists. It stops short of naming create_deposit or the reuse tool explicitly, so the alternative is inferred rather than stated.

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

Deploy Server

Other Tools