Skip to main content
Glama
Sign In
iran-crypto-mcp

iran-crypto-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Ticker

ic_get_ticker
Read-onlyIdempotent

Fetches live price, best bid/ask, 24h range, change, and volume for a single coin on a specified Iranian exchange in IRT or USDT.

Instructions

Get the live price, best bid and ask, 24h range, change and volume of one coin on one exchange.

Bid and ask are missing for Bitpin, Tabdeal, OMPFinex, Exir and Balinex; volume is missing for Tabdeal.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "exchange": "<exchange>",
      "coin": "<coin>"
    },
    "name": "ic_get_ticker"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYesCoin symbol, e.g. 'BTC', 'USDT'
quoteNo'IRT' = Toman market, 'USDT' = Tether marketIRT
exchangeYesExchange id, e.g. 'nobitex'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • changedInput schema / properties / exchange / enum
      Previous value: -[
-  "nobitex",
-  "wallex",
-  "bitpin",
-  "ramzinex",
-  "tabdeal",
-  "ompfinex",
-  "exir",
-  "abantether",
-  "kifpool",
-  "okex",
-  "tetherland",
-  "bit24"
-]New value: +[
+  "nobitex",
+  "wallex",
+  "bitpin",
+  "ramzinex",
+  "tabdeal",
+  "ompfinex",
+  "exir",
+  "abantether",
+  "kifpool",
+  "okex",
+  "tetherland",
+  "bit24",
+  "balinex"
+]
  2. Changed3 schema fields changedv0.4.0
    • changedInput schema / properties / coin / description
      Previous value: -"Coin symbol, e.g. 'BTC', 'ETH', 'USDT' (Tether in Toman), 'TON'"New value: +"Coin symbol, e.g. 'BTC', 'USDT'"
    • changedInput schema / properties / exchange / description
      Previous value: -"Exchange id from ic_list_exchanges, e.g. 'nobitex'"New value: +"Exchange id, e.g. 'nobitex'"
    • changedInput schema / properties / quote / description
      Previous value: -"Quote currency: 'IRT' = Toman market (default), 'USDT' = Tether market"New value: +"'IRT' = Toman market, 'USDT' = Tether market"
  3. Changed1 schema field changedv0.3.0
    • changedInput schema / properties / exchange / enum
      Previous value: -[
-  "nobitex",
-  "wallex",
-  "bitpin",
-  "ramzinex",
-  "tabdeal",
-  "ompfinex",
-  "exir"
-]New value: +[
+  "nobitex",
+  "wallex",
+  "bitpin",
+  "ramzinex",
+  "tabdeal",
+  "ompfinex",
+  "exir",
+  "abantether",
+  "kifpool",
+  "okex",
+  "tetherland",
+  "bit24"
+]
  4. First observedv0.1.2

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds useful behavioral context by disclosing which exchanges lack bid/ask data and that Tabdeal lacks volume, though it does not cover invalid-input behavior or data freshness beyond 'live'.

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?

The description is two sentences, front-loaded with the core purpose and followed by a compact caveat about missing fields per exchange. Every sentence earns its place with no redundancy.

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?

With a fully described schema and no output schema, the description is nearly complete: it lists the returned fields and flags known data gaps. It could be slightly more complete by clarifying output format or timestamp behavior, but it is sufficient for correct invocation.

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

Parameters3/5

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

Schema description coverage is 100%, and both enums are fully documented in the schema. The description adds no parameter-specific meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Get the live price...of one coin on one exchange') and enumerates the returned fields. It clearly identifies the tool as a single-market ticker snapshot, though it does not explicitly differentiate itself from siblings such as ic_compare_price or ic_get_orderbook.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The phrase 'one coin on one exchange' implies usage for a single-market snapshot, which is helpful context. However, there is no explicit guidance on when to use this tool versus alternatives like ic_get_orderbook, ic_candles, or ic_compare_price.

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