Skip to main content
Glama
emercoin

Emercoin swap

Official

Buy EMC with USDT (open an order)

buy_emc

Buy EMC with USDT (TRC20): get a deposit address, transfer the exact amount, and receive EMC automatically at your address.

Instructions

Open an order to buy EMC with USDT (TRC20) and get back a shared TRON deposit_address plus the EXACT amount_usdt to send. This does NOT move funds: you then transfer that exact figure (it is your order's matching tag) to the deposit address; on confirmed payment, EMC (amount_usdt × rate) is delivered to your address automatically. Keep the returned token and poll get_order_status until 'notified'; to abandon before paying, call cancel_order. One-way — a wrong amount cannot be matched and is NOT refunded. By default each call opens a NEW order; pass a stable idempotency_key to make retries return the same order. Use get_swap_config first to pick a valid amount.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amount_usdtYesUSDT to pay; must be one of the allowed denominations from get_swap_config (currently 5 or 10)
destination_emc_addressYesyour EMC address to receive EMC (legacy 'E…' or bech32 'em1…')
idempotency_keyNooptional: a stable string you choose; retrying buy_emc with the same key + address + amount returns the SAME order instead of opening a new one (use it so a retry after a timeout doesn't create a duplicate)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesopaque handle to poll this order
order_idYes
deposit_addressYes
amount_usdtYesEXACT amount to send — pay this figure
emc_amountYes
statusYes
expires_atYes
Behavior5/5

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

Discloses that no funds are moved, the exact amount must be sent, it's one-way, wrong amount not refunded, and idempotency_key behavior. Adds context beyond 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?

Well-structured and front-loaded, but slightly verbose; each sentence adds value, but could be more concise.

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?

Comprehensively covers the multi-step process, idempotency, refund policy, and expected outputs, making it complete for an agent.

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 three parameters are fully described in both schema and description, with additional context on allowed amounts and idempotency key usage.

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 it opens an order to buy EMC with USDT, detailing the process and distinguishing from siblings like cancel_order, get_order_status, get_swap_config.

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 tells when to use (buy EMC), when not to (wrong amount not refunded), and recommends using get_swap_config first. Also explains retry behavior and polling.

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/emercoin/swap'

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