AIsa Finance

Coins List with Market Data

get_coingecko_coins_markets

Read-onlyIdempotent

This endpoint allows you to query all the supported coins with price, market cap, volume and market related data

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

Name	Required	Description	Default
`ids`	No	Coins' IDs, comma-separated if querying more than 1 coin. *refers to [`/coins/list`](/reference/coins-list)	bitcoin
`page`	No	Page through results. Default: 1
`names`	No	Coins' names, comma-separated if querying more than 1 coin.	Bitcoin
`order`	No	Sort result by field. Default: market_cap_desc
`locale`	No	Language background. Default: en
`symbols`	No	Coins' symbols, comma-separated if querying more than 1 coin.	btc
`category`	No	Filter based on coins' category. *refers to [`/coins/categories/list`](/reference/coins-categories-list)
`per_page`	No	Total results per page. Default: 100 Valid values: 1...250
`precision`	No	Decimal places for currency price value
`sparkline`	No	Include sparkline 7-day data. Default: false
`vs_currency`	Yes	Target currency of coins and market data. *refers to [`/simple/supported_vs_currencies`](/reference/simple-supported-currencies)	usd
`include_tokens`	No	For `symbols` lookups, specify `all` to include all matching tokens. Default `top` returns top-ranked tokens by market cap or volume.
`include_rehypothecated`	No	Include rehypothecated tokens in results. When true, returns `market_cap_rank_with_rehypothecated` field. Default: false
`price_change_percentage`	No	Include price change percentage timeframe, comma-separated if querying more than 1 timeframe. Valid values: `1h`, `24h`, `7d`, `14d`, `30d`, `200d`, `1y`

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed29 schema fields changedOct 15, 2026

changedInput schema / properties / category / description

Previous value: -"Filter by category (see `/coins/categories/list`)."New value: +"Filter based on coins' category. \n*refers to [`/coins/categories/list`](/reference/coins-categories-list)"

addedInput schema / properties / ids / default
```
Added value: +"bitcoin"
```

changedInput schema / properties / ids / description

Previous value: -"Comma-separated CoinGecko coin IDs."New value: +"Coins' IDs, comma-separated if querying more than 1 coin. \n*refers to [`/coins/list`](/reference/coins-list)"

removedInput schema / properties / ids / example
```
Removed value: -"bitcoin,ethereum"
```
removedInput schema / properties / include_rehypothecated / default
```
Removed value: -false
```

changedInput schema / properties / include_rehypothecated / description

Previous value: -"Include rehypothecated tokens in market data when supported by CoinGecko."New value: +"Include rehypothecated tokens in results. When true, returns `market_cap_rank_with_rehypothecated` field. \nDefault: false"

addedInput schema / properties / include_tokens

Added value: +{
+  "description": "For `symbols` lookups, specify `all` to include all matching tokens. \nDefault `top` returns top-ranked tokens by market cap or volume.",
+  "enum": [
+    "top",
+    "all"
+  ],
+  "type": "string"
+}

removedInput schema / properties / locale / default
```
Removed value: -"en"
```

changedInput schema / properties / locale / description

Previous value: -"Response language locale. Official values include `en`, `zh`, `zh-tw`, and other supported CoinGecko locales."New value: +"Language background. \nDefault: en"

addedInput schema / properties / locale / enum

Added value: +[
+  "ar",
+  "bg",
+  "cs",
+  "da",
+  "de",
+  "el",
+  "en",
+  "es",
+  "fi",
+  "fr",
+  "he",
+  "hi",
+  "hr",
+  "hu",
+  "id",
+  "it",
+  "ja",
+  "ko",
+  "lt",
+  "nl",
+  "no",
+  "pl",
+  "pt",
+  "ro",
+  "ru",
+  "sk",
+  "sl",
+  "sv",
+  "th",
+  "tr",
+  "uk",
+  "vi",
+  "zh",
+  "zh-tw"
+]

removedInput schema / properties / locale / example
```
Removed value: -"en"
```

addedInput schema / properties / names

Added value: +{
+  "default": "Bitcoin",
+  "description": "Coins' names, comma-separated if querying more than 1 coin.",
+  "type": "string"
+}

removedInput schema / properties / order / default
```
Removed value: -"market_cap_desc"
```

addedInput schema / properties / order / description

Added value: +"Sort result by field. \nDefault: market_cap_desc"

changedInput schema / properties / order / enum

Previous value: -[
-  "market_cap_desc",
-  "market_cap_asc",
-  "volume_desc",
-  "volume_asc",
-  "id_asc",
-  "id_desc"
-]New value: +[
+  "market_cap_asc",
+  "market_cap_desc",
+  "volume_asc",
+  "volume_desc",
+  "id_asc",
+  "id_desc"
+]

removedInput schema / properties / page / default
```
Removed value: -1
```

addedInput schema / properties / page / description

Added value: +"Page through results. \nDefault: 1"

removedInput schema / properties / per_page / default
```
Removed value: -100
```

addedInput schema / properties / per_page / description

Added value: +"Total results per page. \nDefault: 100 \nValid values: 1...250"

removedInput schema / properties / per_page / maximum
```
Removed value: -250
```
removedInput schema / properties / per_page / minimum
```
Removed value: -1
```

changedInput schema / properties / precision / description

Previous value: -"`full` or a value from `0` to `18` to specify decimal places for currency price values."New value: +"Decimal places for currency price value"

addedInput schema / properties / precision / enum

Added value: +[
+  "full",
+  "0",
+  "1",
+  "2",
+  "3",
+  "4",
+  "5",
+  "6",
+  "7",
+  "8",
+  "9",
+  "10",
+  "11",
+  "12",
+  "13",
+  "14",
+  "15",
+  "16",
+  "17",
+  "18"
+]

removedInput schema / properties / precision / example
```
Removed value: -"2"
```

changedInput schema / properties / price_change_percentage / description

Previous value: -"Comma-separated windows: `1h,24h,7d,14d,30d,200d,1y`."New value: +"Include price change percentage timeframe, comma-separated if querying more than 1 timeframe. \nValid values: `1h`, `24h`, `7d`, `14d`, `30d`, `200d`, `1y`"

removedInput schema / properties / sparkline / default
```
Removed value: -false
```

addedInput schema / properties / sparkline / description

Added value: +"Include sparkline 7-day data. \nDefault: false"

addedInput schema / properties / symbols

Added value: +{
+  "default": "btc",
+  "description": "Coins' symbols, comma-separated if querying more than 1 coin.",
+  "type": "string"
+}

changedInput schema / properties / vs_currency / description

Previous value: -"Target currency for price (e.g., `usd`, `eur`, `btc`). See `/simple/supported_vs_currencies`."New value: +"Target currency of coins and market data. \n*refers to [`/simple/supported_vs_currencies`](/reference/simple-supported-currencies)"

Changed3 schema fields changedSep 18, 2026
- addedInput schema / properties / ids / example
```
Added value: +"bitcoin,ethereum"
```
- addedInput schema / properties / locale / example
```
Added value: +"en"
```
- addedInput schema / properties / precision / example
```
Added value: +"2"
```
First observedSep 15, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds no behavioral context beyond that — no pagination behavior, no rate-limit or quota notes, no indication of result size or cost implications beyond the boilerplate pricing line.

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?

A single front-loaded sentence states the purpose immediately, with the pricing block appended as required boilerplate. Nothing is padded or redundant, though the sentence is arguably too sparse for a 14-parameter tool rather than truly 'concise'.

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

Completeness2/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 no explanation, and annotations cover the safety profile. But for a 14-parameter, highly configurable endpoint sitting among many overlapping CoinGecko siblings, the description omits any differentiation or scoping guidance an agent needs to select it correctly.

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 14 parameters (including enums for order, locale, precision, include_tokens) are already documented in the schema. The description adds nothing parameter-specific, which matches the baseline 3 when the schema does the heavy lifting.

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 clear verb and resource: query all supported coins with price, market cap, volume and market-related data. An agent knows what it returns. However, it does not distinguish this tool from close siblings like get_coingecko_coins_list, get_coingecko_simple_price, or get_coingecko_coins_id, so the 'which one do I call' question is left open.

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 guidance, no stated prerequisites, and no mention of alternatives in a sibling set of 27 tools. With get_coingecko_coins_list, get_coingecko_simple_price, and get_coingecko_coins_id all plausibly overlapping, the absence of routing guidance is a real gap.

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

All AIsa Finance tools Inspect

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

Need Help?