AIsa Finance

Coin Price by Token Addresses

get_coingecko_simple_token_price_id

Read-onlyIdempotent

This endpoint allows you to query one or more token prices using their token contract addresses

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "contract_addresses": "<contract_addresses>",
      "vs_currencies": "<vs_currencies>"
    },
    "name": "get_coingecko_simple_token_price_id"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Asset platform's ID. *refers to [`/asset_platforms`](/reference/asset-platforms-list)	ethereum
`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). For the complete list of fiat currencies supported by this endpoint, see [Fiat Currencies Support List](/docs/fiat-currencies-support).	usd
`include_24hr_vol`	No	Include 24-hour trading volume. Default: false
`contract_addresses`	Yes	Token contract addresses, comma-separated if querying more than 1 token	0x2260fac5e5542a773aa44fbcfedf7c193bc2c599
`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.

Changed1 schema field changedNov 1, 2026

changedInput schema / properties / vs_currencies / description

Previous value: -"Target currency of coins, comma-separated if querying more than 1 currency. \n*refers to [`/simple/supported_vs_currencies`](/reference/simple-supported-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). \n\nFor the complete list of fiat currencies supported by this endpoint, see [Fiat Currencies Support List](/docs/fiat-currencies-support)."

Changed16 schema fields changedOct 15, 2026

addedInput schema / properties / contract_addresses / default

Added value: +"0x2260fac5e5542a773aa44fbcfedf7c193bc2c599"

changedInput schema / properties / contract_addresses / description

Previous value: -"Comma-separated contract addresses."New value: +"Token contract addresses, comma-separated if querying more than 1 token"

removedInput schema / properties / contract_addresses / example

Removed value: -"0xdAC17F958D2ee523a2206206994597C13D831ec7"

addedInput schema / properties / id / default
```
Added value: +"ethereum"
```

changedInput schema / properties / id / description

Previous value: -"Platform ID (e.g., `ethereum`, `binance-smart-chain`, `polygon-pos`)."New value: +"Asset platform's ID. \n*refers to [`/asset_platforms`](/reference/asset-platforms-list)"

removedInput schema / properties / id / example
```
Removed value: -"ethereum"
```

addedInput schema / properties / include_24hr_change / description

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

addedInput schema / properties / include_24hr_vol / description

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

addedInput schema / properties / include_last_updated_at / description

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

addedInput schema / properties / include_market_cap / description

Added value: +"Include market capitalization. \nDefault: false"

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"
```
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"
```

Changed4 schema fields changedSep 18, 2026
- addedInput schema / properties / contract_addresses / example
```
Added value: +"0xdAC17F958D2ee523a2206206994597C13D831ec7"
```
- addedInput schema / properties / id / example
```
Added value: +"ethereum"
```
- addedInput schema / properties / precision / example
```
Added value: +"2"
```
- addedInput schema / properties / vs_currencies / example
```
Added value: +"usd"
```
First observedSep 15, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description contributes a cost disclosure (~$0.008 per successful request), which is genuinely useful for a paid, open-world lookup. Beyond that it says nothing about caching, data freshness, or failure modes when an address is unknown on the given platform.

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 stating the operation, with the pricing note cleanly separated. Minor waste in the boilerplate 'This endpoint allows you to' phrasing and markdown emphasis, but nothing structurally misplaced.

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. However, for an 8-parameter tool the description omits a critical dependency: contract addresses are only meaningful relative to the id asset platform (default 'ethereum'), so an agent can easily submit addresses for the wrong chain without being warned.

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 coverage is 100% with per-field descriptions for all eight parameters, so the schema carries the load and the baseline is 3. The description's 'one or more token prices' lightly reinforces comma-separated batching, but it adds no semantics for id, precision, vs_currencies, or the four include_* toggles.

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 and resource: query token prices by token contract addresses, with explicit support for multiple tokens. The mechanism (contract addresses) implicitly separates it from the id-based get_coingecko_simple_price, but no sibling is named, so an agent must infer the distinction.

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 statement of when to use this versus get_coingecko_simple_price, get_coingecko_token_data, or the market-chart variants. The only hint is the phrase 'using their token contract addresses', which lets an agent infer the intended input type but gives no exclusions or prerequisites.

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?