Skip to main content
Glama

AIsa Finance

by one.aisa
OverviewDiscussionsAdmin

Coin Tickers by ID

get_coingecko_coins_id_tickers
Read-onlyIdempotent

This endpoint allows you to query the coin tickers on both centralized exchange (CEX) and decentralized exchange (DEX) based on a particular coin 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
idYesCoin ID. *refers to [`/coins/list`](/reference/coins-list)bitcoin
pageNoPage through results
depthNoInclude 2% orderbook depth, i.e. `cost_to_move_up_usd` and `cost_to_move_down_usd`. Default: false
orderNoSort the order of responses. Default: trust_score_desc
exchange_idsNoExchange ID. *refers to [`/exchanges/list`](/reference/exchanges-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. Changed13 schema fields changed
    • removedInput schema / properties / depth / default
      Removed value: -false
    • addedInput schema / properties / depth / description
      Added value: +"Include 2% orderbook depth, i.e. `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"
+}
    • changedInput schema / properties / exchange_ids / description
      Previous value: -"Comma-separated exchange IDs."New value: +"Exchange ID. \n*refers to [`/exchanges/list`](/reference/exchanges-list)"
    • addedInput schema / properties / id / default
      Added value: +"bitcoin"
    • changedInput schema / properties / id / description
      Previous value: -"CoinGecko coin ID (e.g., `bitcoin`, `ethereum`). Get the list via `/coins/list`."New value: +"Coin ID. \n*refers to [`/coins/list`](/reference/coins-list)"
    • removedInput schema / properties / id / example
      Removed value: -"bitcoin"
    • 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: +[
+  "trust_score_desc",
+  "trust_score_asc",
+  "volume_desc",
+  "volume_asc"
+]
    • removedInput schema / properties / page / default
      Removed value: -1
    • addedInput schema / properties / page / description
      Added value: +"Page through results"
  2. Changed1 schema field changed
    • addedInput schema / properties / id / example
      Added value: +"bitcoin"
  3. First observed

TDQS

B3.2/5.0
Behavior3/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 the CEX/DEX scope but says nothing about pagination, result volume, or rate limits beyond the generic pricing boilerplate.

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 core sentence is a single efficient statement of purpose and is front-loaded. The appended pricing boilerplate is noise for tool selection but is not authored content that dilutes the functional description.

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 an output schema present and 100% parameter coverage, the description needn't explain returns or params. Annotations carry the safety profile, leaving only the lack of sibling/alternative routing as a minor gap.

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 every parameter (id, page, depth, order, exchange_ids, dex_pair_format, include_exchange_logo) is already documented with enums and defaults in the schema. The description contributes no additional parameter meaning, so the baseline 3 applies.

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 gives a specific verb (query) and resource (coin tickers) and scopes it to both CEX and DEX for a given coin ID, which an agent can distinguish from exchange-oriented siblings. It stops short of naming the nearest alternative, get_coingecko_exchanges_id_tickers, so it does not fully self-differentiate.

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 explicit when-to-use or when-not-to-use guidance and no mention of the sibling get_coingecko_exchanges_id_tickers, which retrieves tickers from the exchange side. Usage is only implied by the resource described.

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