Skip to main content
Glama

AIsa Finance

by one.aisa
OverviewDiscussionsAdmin

Exchange Tickers by ID

get_coingecko_exchanges_id_tickers
Read-onlyIdempotent

This endpoint allows you to query exchange's tickers based on exchange's ID

Published reference price: $0.008 USD per successful request. Declared unit rate: $0 USD per provider_credit. Account-specific pricing and final settlement may differ.

Input Schema

NameRequiredDescriptionDefault
idYesExchange ID. *refers to [`/exchanges/list`](/reference/exchanges-list).binance
pageNoPage through results.
depthNoInclude 2% orderbook depth (cost_to_move_up_usd and cost_to_move_down_usd). Default: false
orderNoSort the order of responses. Default: `trust_score_desc`
coin_idsNoFilter tickers by coin IDs, comma-separated if querying more than 1 coin. *refers to [`/coins/list`](/reference/coins-list).
dex_pair_formatNoSet to `symbol` to display DEX pair base and target as symbols. Default: `contract_address`
include_exchange_logoNoInclude exchange logo. Default: false

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • changedInput schema / properties / coin_ids / description
      Previous value: -"Filter by coin IDs (comma-separated)."New value: +"Filter tickers by coin IDs, comma-separated if querying more than 1 coin. \n*refers to [`/coins/list`](/reference/coins-list)."
    • removedInput schema / properties / depth / default
      Removed value: -false
    • addedInput schema / properties / depth / description
      Added value: +"Include 2% orderbook depth (cost_to_move_up_usd and cost_to_move_down_usd). \nDefault: false"
    • addedInput schema / properties / dex_pair_format
      Added value: +{
+  "description": "Set to `symbol` to display DEX pair base and target as symbols. \nDefault: `contract_address`",
+  "enum": [
+    "contract_address",
+    "symbol"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / id / default
      Added value: +"binance"
    • changedInput schema / properties / id / description
      Previous value: -"CoinGecko exchange ID (e.g., `binance`, `gdax`). Get the list via `/exchanges/list`."New value: +"Exchange ID. \n*refers to [`/exchanges/list`](/reference/exchanges-list)."
    • removedInput schema / properties / id / example
      Removed value: -"binance"
    • removedInput schema / properties / include_exchange_logo / default
      Removed value: -false
    • changedInput schema / properties / include_exchange_logo / description
      Previous value: -"Show exchange logos in ticker results."New value: +"Include exchange logo. \nDefault: false"
    • addedInput schema / properties / order / description
      Added value: +"Sort the order of responses. \nDefault: `trust_score_desc`"
    • changedInput schema / properties / order / enum
      Previous value: -[
-  "trust_score_desc",
-  "trust_score_asc",
-  "volume_desc"
-]New value: +[
+  "market_cap_asc",
+  "market_cap_desc",
+  "trust_score_desc",
+  "trust_score_asc",
+  "volume_desc",
+  "volume_asc",
+  "base_target"
+]
    • removedInput schema / properties / page / default
      Removed value: -1
    • addedInput schema / properties / page / description
      Added value: +"Page through results."
    • changedInput schema / properties / page / type
      Previous value: -"integer"New value: +"number"
  2. Changed1 schema field changed
    • addedInput schema / properties / id / example
      Added value: +"binance"
  3. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds nothing behavioral beyond that – no pagination notes despite the 'page' param, no sort default behavior, no data-freshness or rate-limit context. The pricing boilerplate is billing metadata, not behavioral guidance.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The core sentence is short and front-loaded, but it is padded with the 'This endpoint allows you to' frame and a multi-line pricing block that consumes most of the text without aiding tool selection. The meaningful content is a single clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need not be explained, and annotations cover safety. But for a 7-param, paginated, sortable list endpoint the description omits pagination semantics, default sort, and when to prefer it over sibling ticker tools, leaving it only minimally adequate.

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%, so all seven parameters (including page, depth, order, coin_ids) are already documented in the schema. The description adds no syntax, format, or default guidance beyond what the schema provides, which is the baseline 3 case.

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 clear verb (query) and resource (exchange's tickers) bounded by exchange ID, which distinguishes it from get_coingecko_coins_id_tickers and get_coingecko_exchanges_id. However, the 'This endpoint allows you to' wrapper is filler and the purpose is not contrasted against those siblings explicitly.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus the many sibling ticker/exchange endpoints (get_coingecko_exchanges_id, get_coingecko_coins_id_tickers, get_coingecko_exchanges). The only implicit signal is the 'based on exchange's ID' scoping, with no exclusions or prerequisites stated.

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

All AIsa Finance toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources