Skip to main content
Glama
Bitget-AI

Bitget Agent MCP

Official
by Bitget-AI

withdraw

Submit irreversible crypto transfers (confirm required) or retrieve transfer history. Choose submit to send funds out, records to view past activity.

Instructions

[VERB] Withdrawals by intent: submit (send funds out — irreversible, needs confirm) | records (withdrawal history).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoAddress Tag This is required for withdrawals of certain cryptocurrencies, like EOS.
coinNoCoin to withdraw, e.g. USDT.
sizeNoWithdrawal Quantity Special Notes for Bitcoin Lightning Network Withdrawals: This parameter must exactly match the amount on the Bitcoin Lightning Network deposit invoice; The withdrawal quantity for Bitcoin Lightning Network represents the amount received, excluding fees; The quantity precision can be obtained via the "Get Currency Information" API
viewNosummary (default) trims null fields to save tokens; full returns the untouched payload.
chainNoChain/network for the withdrawal.
limitNoItems per page The default value is 20, and the maximum value is 100.
actionYesWhat to do — submit: submit a withdrawal (irreversible) (needs: coin, transferType, address, size) | records: withdrawal history (needs: startTime, endTime).
amountNoAmount to withdraw.
cursorNoCursor ID - Used for pagination to reduce query response time - Do not send for the initial query. When querying the second page and subsequent data, use the smallest orderId returned from the previous query. The results will return data less than that value
dryRunNoPreview a write without sending it.
fieldsNoOptional list (array or comma-separated string) of fields to keep on each returned row.
remarkNoRemark
addressNoDestination address.
confirmNoRequired to execute destructive (high-risk) writes; without it such a call returns { confirmationRequired: true }.
endTimeNoQuery record end time<ul><li>Unix millisecond timestamp, e.g., 1690196141868</li></ul>
orderIdNoorder ID - Either clientOid or orderId must be provided. If both are present or do not match, orderId will take priority
areaCodeNoArea Code This parameter is required when innerToType = mobile
fetchAllNoPaged reads only: walk the cursor to bounded completion (returns { items, pages, truncated }).
lastNameNoLast Name Fill in this parameter when identity=user
clientOidNoIdempotency key. Auto-generated for `submit` when omitted (P7).
firstNameNoFirst Name Fill in this parameter when identity=user
startTimeNoQuery record start time<ul><li>Unix millisecond timestamp, e.g., 1690196141868</li></ul>
memberCodeNoMember Code bithumb korbit coinone
companyNameNoCompany Name Fill in this parameter when identity=company
innerToTypeNoInternal Withdrawal Address Type uidUser ID email Email mobile Mobile phone number - If not filled, the default value is uid
identityTypeNoIdentity Type companyInstitutional Company user Individual User
transferTypeNoWithdrawal Type on_chainOn-chain deposit internal_transferInternal transfer
Behavior4/5

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

Beyond annotations (readOnlyHint=false, idempotentHint=false), the description adds that submit is 'irreversible' and 'needs confirm', and that records is the history view. This gives important behavioral warnings not present in the annotations. No contradiction with annotations.

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?

The description is a single compact sentence that conveys the core operation split. The '[VERB]' placeholder is a minor flaw, but otherwise every word earns its place.

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?

For a tool with 27 parameters and two intents, the description provides a high-level map of behavior and key requirements. The schema handles detailed parameter semantics, so the description's brevity is acceptable, though it could mention confirm more.

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 description groups required parameters by intent ('submit needs...', 'records needs...'), which is not obvious from the flat schema. Since schema coverage is 100%, this grouping adds practical semantic value.

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 identifies the tool as 'Withdrawals' and distinguishes two intents: 'submit' for sending funds out and 'records' for history. This clearly separates it from sibling tools like deposit and transfer_funds, and the resource is explicit.

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?

The description tells the agent when to use each intent: 'submit' requires coin, transferType, address, size; 'records' requires startTime, endTime. It also warns that submit is irreversible and needs confirmation, which is key usage context. It does not explicitly name alternative tools, but the intent split provides sufficient guidance.

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/Bitget-AI/agent-mcp'

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