Skip to main content
Glama
dwin-gharibi

ramzinex-mcp

by dwin-gharibi

ramzinex_submit_withdraw

Submit a withdrawal request to move real funds from your Ramzinex account to an external wallet. Requires enabled withdrawals and careful verification as transactions are irreversible.

Instructions

Submit a withdrawal request — WARNING: this moves REAL funds.

Persian purpose: ثبت درخواست برداشت (انتقال وجه واقعی). Requires configured credentials AND enable_withdrawals=true (and read_only=false) on the instance; otherwise it returns {"error": "withdrawals_disabled", ...} without contacting the API. Maps to POST /exchange/api/{ver}/exchange/users/me/funds/withdraws/currency/{currency_id} with body {amount, address, network_id, tag?, no_tag}. no_tag is derived automatically (true when no tag is provided).

Double-check the currency, network, address, and amount before calling — withdrawals are irreversible.

Args: currency_id: Numeric id of the currency to withdraw. amount: Amount to withdraw (must be > 0). address: Destination wallet address (non-empty). network_id: Numeric id of the withdrawal network (must be > 0; discover via ramzinex_get_networks). tag: Optional memo/tag/destination tag for networks that require it (e.g. XRP, TON). Omit for networks that do not. instance: Configured instance to use (default when omitted).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
currency_idYes
amountYes
addressYes
network_idYes
tagNo
instanceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description discloses key behaviors: moves real funds, irreversible, requires specific config, and returns error if disabled. It doesn't cover all possible error states but is sufficient for safe usage.

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?

Well-structured with a clear hierarchy: warning, purpose, config, API mapping, parameter list. Slightly verbose but every sentence adds value; could be tightened slightly.

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?

Comprehensive for a withdrawal tool with output schema. Covers prerequisites, parameter semantics, and usage warnings. Lacks details on success response or additional error codes, but output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 6 parameters are described with constraints and context (e.g., tag for XRP/TON, no_tag derived, network_id discoverable via ramzinex_get_networks). Schema coverage is 0%, so this fully compensates.

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 clearly states 'Submit a withdrawal request' with a warning about moving real funds. It specifies the action and resource, distinguishing it from query tools like ramzinex_get_withdraws.

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?

Includes prerequisites (enable_withdrawals=true, read_only=false) and advises to double-check details due to irreversibility. However, it doesn't explicitly mention when not to use it or suggest alternatives like ramzinex_confirm_withdraw.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dwin-gharibi/ramzinex-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server