Skip to main content
Glama

AIsa Finance

by one.aisa
OverviewDiscussionsAdmin

Exchange Data by ID

get_coingecko_exchanges_id
Read-onlyIdempotent

This endpoint allows you to query exchange's data (name, year established, country, ...), exchange volume in BTC and top 100 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

TableJSON Schema
NameRequiredDescriptionDefault
idYesExchange ID. *refers to [`/exchanges/list`](/reference/exchanges-list).binance
dex_pair_formatNoSet to `symbol` to display DEX pair base and target as symbols. Default: `contract_address`

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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"
  2. Changed1 schema field changed
    • addedInput schema / properties / id / example
      Added value: +"binance"
  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 what payload is returned and a pricing note, which is useful, but does not address pagination, rate limits, or auth, so it adds only moderate value 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.

Conciseness4/5

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

The purpose is front-loaded in a single sentence with no filler; the only additional text is the auto-inserted pricing block. The sentence is slightly run-on with the enumeration of fields, but it is not padded.

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?

With an output schema present, return-value explanation is not strictly required, and annotations cover the safety profile, so the definition is largely adequate. The notable gap is guidance on when to pick this over the sibling list/tickers endpoints.

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 the id and dex_pair_format parameters are fully documented in the schema. The description only restates that the lookup is keyed by exchange ID, adding no syntax or format detail beyond what the schema provides.

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?

States a specific verb (query) and resource (exchange data: name, year established, country, volume in BTC, top 100 tickers) keyed by exchange ID. It is distinguishable from get_coingecko_exchanges (list) and get_coingecko_exchanges_list, though the mention of 'top 100 tickers' overlaps with the dedicated get_coingecko_exchanges_id_tickers sibling, creating mild ambiguity.

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 guidance, no exclusions, and no routing to alternatives such as get_coingecko_exchanges or get_coingecko_exchanges_id_tickers. Usage is only implied by the 'based on exchange's ID' phrasing.

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