Skip to main content
Glama
emercoin

Emercoin swap

Official
by emercoin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get EMC swap limits and rate

get_swap_config
Read-onlyIdempotent

Get the fixed USDT denominations and current EMC rate to choose a valid amount for buying EMC.

Instructions

Return the current order denominations and fixed rate for buying EMC with USDT. allowed_amounts is the exact set of USDT values buy_emc accepts (fixed denominations, not a free range) — pick one of these; min_usdt/max_usdt are its bounds and emc_per_usdt is the rate (EMC you receive = amount_usdt × emc_per_usdt). Call this first to choose a valid amount for buy_emc. Read-only — it neither creates nor changes an order. support_email is the operator contact for manual cases (e.g. an order on aml_hold or a late/mismatched payment).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
min_usdtYes
max_usdtYes
allowed_amountsNothe fixed USDT denominations a buyer may pick
emc_per_usdtYes
support_emailNooperator contact for manual cases

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / allowed_amounts
      Added value: +{
+  "description": "the fixed USDT denominations a buyer may pick",
+  "items": {
+    "type": "number"
+  },
+  "title": "Allowed Amounts",
+  "type": "array"
+}
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint. Description adds that it 'neither creates nor changes an order' and explains the support_email for manual cases, going 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every sentence adds value. Well-structured: purpose, field explanations, usage guidance, read-only note, support contact. No fluff.

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?

Given zero parameters, rich annotations, and low complexity, the description fully covers what the tool does and how to use it. Output schema exists but description complements it.

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?

No parameters, so baseline is 4. Description adds value by explaining output fields, which helps in understanding the tool's result.

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?

Clearly states it returns current order denominations and fixed rate for buying EMC with USDT. It distinguishes itself from sibling buy_emc by implying it's a prerequisite.

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?

Explicitly says 'Call this first to choose a valid amount for buy_emc.' Provides clear context for when to use it relative to siblings.

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