Skip to main content
Glama
Sign In

AIsa Finance

by one.aisa
OverviewDiscussionsAdmin

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.

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": {
      "vs_currencies": "<vs_currencies>"
    },
    "name": "get_coingecko_simple_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNoCoins' IDs, comma-separated if querying more than 1 coin. *refers to [`/coins/list`](/reference/coins-list)bitcoin
namesNoCoins' names, comma-separated if querying more than 1 coin.Bitcoin
symbolsNoCoins' symbols, comma-separated if querying more than 1 coin.btc
precisionNoDecimal places for currency price value
vs_currenciesYesTarget 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_tokensNoFor `symbols` lookups, specify `all` to include all matching tokens. Default `top` returns top-ranked tokens by market cap or volume.
include_24hr_volNoInclude 24-hour trading volume. Default: false
include_market_capNoInclude market capitalization. Default: false
include_24hr_changeNoInclude 24-hour change percentage. Default: false
include_last_updated_atNoInclude last updated price time as a UNIX timestamp. Default: false

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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)."
  2. Changed20 schema fields changed
    • 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"
+]
  3. Changed2 schema fields changed
    • addedInput schema / properties / ids / example
      Added value: +"bitcoin,ethereum"
    • addedInput schema / properties / vs_currencies / example
      Added value: +"usd,eur"
  4. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare this a read-only, idempotent, non-destructive open-world call, so the safety profile is covered. The description adds a published per-request price ($0.008/request), which is useful cost context, but nothing about rate limits, symbol ambiguity, or response behavior beyond what the schema already states.

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 statement is one front-loaded sentence with no wasted words. The appended pricing block is boilerplate but informative and clearly delineated.

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 and annotations cover safety, so the remaining gap is guidance for a 10-parameter tool: which lookup key to choose and how this differs from sibling price endpoints. For a moderately complex endpoint the description is adequate but leaves the agent to infer selection.

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 every parameter is already documented in the schema, including the enum choices for precision and include_tokens. The description adds no extra meaning about how ids, symbols, and names interact or about the one-required-parameter constraint.

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 has a specific verb (query prices) and resource (coins), and it names the three lookup keys (IDs, symbols, names), which matches the schema. It does not, however, distinguish this tool from close siblings such as get_coingecko_simple_token_price_id or get_coingecko_coins_id.

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?

It says nothing about when to use this tool versus the many other price and coin endpoints in the sibling list, and it gives no exclusions or prerequisites. The intended usage (get a lightweight price quote) is only inferred from the word 'price'.

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