AIsa Finance

Coin Price by IDs, Symbols, or Names

get_coingecko_simple_price

Read-onlyIdempotent

This endpoint allows you to query the prices of one or more coins by using their unique Coin API IDs, symbols, or names

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
`names`	No	Coins' names, comma-separated if querying more than 1 coin.	Bitcoin
`symbols`	No	Coins' symbols, comma-separated if querying more than 1 coin.	btc
`precision`	No	Decimal places for currency price value
`vs_currencies`	Yes	Target currency of coins, comma-separated if querying more than 1 currency. *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_24hr_vol`	No	Include 24-hour trading volume. Default: false
`include_market_cap`	No	Include market capitalization. Default: false
`include_24hr_change`	No	Include 24-hour change percentage. Default: false
`include_last_updated_at`	No	Include last updated price time as a UNIX timestamp. Default: false

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedOct 15, 2026

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

changedInput schema / properties / ids / description

Previous value: -"Comma-separated 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_24hr_change / default
```
Removed value: -false
```

addedInput schema / properties / include_24hr_change / description

Added value: +"Include 24-hour change percentage. \nDefault: false"

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

addedInput schema / properties / include_24hr_vol / description

Added value: +"Include 24-hour trading volume. \nDefault: false"

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

addedInput schema / properties / include_last_updated_at / description

Added value: +"Include last updated price time as a UNIX timestamp. \nDefault: false"

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

addedInput schema / properties / include_market_cap / description

Added value: +"Include market capitalization. \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"
+}

addedInput schema / properties / names

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

addedInput schema / properties / precision / description

Added 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"
+]

addedInput schema / properties / symbols

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

addedInput schema / properties / vs_currencies / default
```
Added value: +"usd"
```

changedInput schema / properties / vs_currencies / description

Previous value: -"Comma-separated target currencies."New value: +"Target currency of coins, comma-separated if querying more than 1 currency. \n*refers to [`/simple/supported_vs_currencies`](/reference/simple-supported-currencies)"

removedInput schema / properties / vs_currencies / example
```
Removed value: -"usd,eur"
```

changedInput schema / required

Previous value: -[
-  "ids",
-  "vs_currencies"
-]New value: +[
+  "vs_currencies"
+]

Changed2 schema fields changedSep 18, 2026
- addedInput schema / properties / ids / example
```
Added value: +"bitcoin,ethereum"
```
- addedInput schema / properties / vs_currencies / example
```
Added value: +"usd,eur"
```
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, and destructiveHint=false, so the safety profile is covered structurally. The description adds no behavioral context beyond the purpose statement — no rate limits, caching, batching behavior, or auth requirements — so it contributes little beyond the annotations.

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 purpose is a single front-loaded sentence, which is good. However, the injected aisa-pricing boilerplate adds three lines of billing text irrelevant to tool selection or invocation, diluting an otherwise tight description.

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 no explanation, and the schema fully covers parameters while annotations cover safety. The remaining gap is routing guidance against the many sibling price/coin tools, which the description does not address.

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 schema already documents all 10 parameters including the enum constraints and comma-separated syntax. The description adds no syntax or semantic detail beyond what the schema provides, making the baseline 3 appropriate.

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 the prices') and resource ('one or more coins') plus the three lookup keys (IDs, symbols, names), which maps cleanly to the title. It does not, however, distinguish itself from close siblings like get_coingecko_simple_token_price_id or get_coingecko_coins_markets, so an agent cannot route between them from this text alone.

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 prerequisites, and no mention of when a different sibling (e.g. token_price_id, markets, or coins_id_history) would be preferable. The agent is left to infer usage purely from the endpoint name.

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?