Emercoin swap

Buy EMC with USDT (open an order)

buy_emc

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

Name	Required	Description
`amount_usdt`	Yes	USDT to pay; must be one of the allowed denominations from get_swap_config (currently 5 or 10)
`idempotency_key`	No	optional: 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)
`destination_emc_address`	Yes	your EMC address to receive EMC (legacy 'E…' or bech32 'em1…')

Output Schema

TableJSON Schema

Name	Required	Description
`token`	Yes	opaque handle to poll this order
`status`	Yes
`order_id`	Yes
`emc_amount`	Yes
`expires_at`	Yes
`amount_usdt`	Yes	EXACT amount to send — pay this figure
`deposit_address`	Yes

TDQS

A4.3/5.0

Behavior4/5

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

The description clarifies that the tool does NOT move funds, describes the payment flow, and idempotency behavior. It does not contradict annotations (readOnlyHint=false, etc.) and adds beyond them.

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 front-loaded with the core action and process. It is somewhat lengthy but each sentence adds value. Could be slightly more concise, but well-structured.

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?

Given the complexity (financial transaction, multiple steps), the description covers the flow, safety warnings, idempotency, and ties to siblings. Output schema exists but is not shown; still fairly complete.

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%, but the description adds meaning: amount_usdt must be from allowed denominations, idempotency_key explanation for retries, destination_emc_address format examples.

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 explicitly states 'Open an order to buy EMC with USDT' and outlines the complete process, distinguishing it from sibling tools like cancel_order, get_order_status, and 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It advises to use get_swap_config first to pick a valid amount, explains idempotency for retries, and warns that wrong amounts are not refunded. It covers when to use but could be more explicit about when not to use.

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

All Emercoin swap tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0

Disambiguation5/5

Each tool has a distinct purpose: creating an order, cancelling it, checking its status, and fetching configuration. No overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., buy_emc, cancel_order), making them predictable.

Tool Count5/5

With 4 tools, the set is well-scoped for the specific domain of EMC-USDT swaps, covering all necessary actions without bloat.

Completeness5/5

The tools cover the full lifecycle: get configuration, create an order, check status, and cancel before payment. No obvious missing operations for this narrow domain.

Resources

Need Help?