Skip to main content
Glama

AIsa Finance

by one.aisa
OverviewDiscussionsAdmin

Coin Data by ID

get_coingecko_coins_id
Read-onlyIdempotent

This endpoint allows you to query all the metadata (image, websites, socials, description, contract address, etc.) and market data (price, ATH, exchange tickers, etc.) of a coin from the CoinGecko coin page 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
tickersNoInclude tickers data. Default: true
sparklineNoInclude sparkline 7-day data. Default: false
market_dataNoInclude market data. Default: true
localizationNoInclude all localized languages in the response. Default: true
community_dataNoInclude community data. Deprecated: has no effect as of 28 August 2026; the `community_data` object is no longer returned.
developer_dataNoInclude developer data. Deprecated: has no effect as of 28 August 2026; the `developer_data` object is no longer returned.
dex_pair_formatNoSet to `symbol` to display DEX pair base and target as symbols. Default: `contract_address`
include_categories_detailsNoInclude categories details. Default: false

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changed
    • removedInput schema / properties / community_data / default
      Removed value: -true
    • addedInput schema / properties / community_data / description
      Added value: +"Include community data. \nDeprecated: has no effect as of 28 August 2026; the `community_data` object is no longer returned."
    • removedInput schema / properties / developer_data / default
      Removed value: -true
    • addedInput schema / properties / developer_data / description
      Added value: +"Include developer data. \nDeprecated: has no effect as of 28 August 2026; the `developer_data` object is no longer returned."
    • 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: +"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)"
    • addedInput schema / properties / include_categories_details
      Added value: +{
+  "description": "Include categories details. \nDefault: false",
+  "type": "boolean"
+}
    • removedInput schema / properties / localization / default
      Removed value: -true
    • addedInput schema / properties / localization / description
      Added value: +"Include all localized languages in the response. \nDefault: true"
    • removedInput schema / properties / market_data / default
      Removed value: -true
    • addedInput schema / properties / market_data / description
      Added value: +"Include market data. \nDefault: true"
    • removedInput schema / properties / sparkline / default
      Removed value: -false
    • addedInput schema / properties / sparkline / description
      Added value: +"Include sparkline 7-day data. \nDefault: false"
    • removedInput schema / properties / tickers / default
      Removed value: -true
    • addedInput schema / properties / tickers / description
      Added value: +"Include tickers data. \nDefault: true"
  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, and destructiveHint=false, so safety is covered. The description adds the scope of returned data and the injected pricing note ($0.008 per successful request), which is genuinely useful cost context, but it says nothing about response size, rate limits, or that booleans control payload composition.

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 statement is one long, markdown-bolded sentence padded with 'This endpoint allows you to', and it is followed by an HTML-comment pricing block that is noise for tool selection. The purpose is front-loaded, but the prose is bloated relative to its information content.

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, the description need not explain return values, and annotations cover the safety profile; combined with a 100%-documented schema, the agent has enough to call it correctly. The remaining gap is ambiguity about when to prefer this over the narrower coin siblings.

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% (9 params, all documented, including deprecation notices for community_data/developer_data and the dex_pair_format enum), so the schema carries the burden. The description's enumeration of returned data loosely maps to the boolean toggles but adds no syntax or default information beyond the schema.

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 (metadata + market data for a coin by coin ID), and enumerates the concrete payload (image, websites, socials, contract address, price, ATH, tickers). An agent can tell this is the broad 'everything about one coin' endpoint, but the description never contrasts it with near-overlapping siblings like get_coingecko_coins_id_tickers, get_coingecko_simple_price, or get_coingecko_coins_id_history.

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 when-to-use / when-not-to-use guidance and no mention of alternatives, despite the sibling set containing several overlapping coin-detail endpoints (tickers, history, market_chart, ohlc). The agent must infer selection purely from the endpoint URL.

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