Skip to main content
Glama

Teardrop

by dev.teardrop.api

Get Token Price

get_token_price
Read-only

Get current price, 24h change, market cap, fully-diluted valuation, and volume for one or more crypto tokens. Accepts ticker symbols (BTC, ETH, LQTY), full token names (Bitcoin, Liquity, Chainlink), or CoinGecko IDs. Unknown symbols are resolved automatically against the full CoinGecko coin list. Supports batch queries up to 50 tokens. Bare 0x contract addresses are not resolvable by CoinGecko and should be treated as unknown. If get_wallet_portfolio already returned price_usd/value_usd for a held token, reuse that value instead of calling get_token_price again.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokensYesToken symbols or CoinGecko IDs (e.g. ['BTC', 'ETH', 'SOL'])
vs_currencyNoQuote currency (usd, eur, gbp, btc, eth)usd

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pricesYes
vs_currencyYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed10 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / tokens / title
      Added value: +"Tokens"
    • addedInput schema / properties / vs_currency / title
      Added value: +"Vs Currency"
    • addedInput schema / title
      Added value: +"mcp_get_token_priceArguments"
    • addedOutput schema / $defs
      Added value: +{
+  "TokenPriceEntry": {
+    "properties": {
+      "change_24h_pct": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Change 24H Pct"
+      },
+      "fully_diluted_valuation": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Fully Diluted Valuation"
+      },
+      "id": {
+        "title": "Id",
+        "type": "string"
+      },
+      "market_cap": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Market Cap"
+      },
+      "price": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Price"
+      },
+      "symbol": {
+        "title": "Symbol",
+        "type": "string"
+      },
+      "volume_24h": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Volume 24H"
+      }
+    },
+    "required": [
+      "id",
+      "symbol",
+      "price",
+      "market_cap",
+      "volume_24h",
+      "change_24h_pct"
+    ],
+    "title": "TokenPriceEntry",
+    "type": "object"
+  }
+}
    • addedOutput schema / properties / prices / items / $ref
      Added value: +"#/$defs/TokenPriceEntry"
    • removedOutput schema / properties / prices / items / properties
      Removed value: -{
-  "change_24h_pct": {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "title": "Change 24H Pct"
-  },
-  "fully_diluted_valuation": {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "title": "Fully Diluted Valuation"
-  },
-  "id": {
-    "title": "Id",
-    "type": "string"
-  },
-  "market_cap": {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "title": "Market Cap"
-  },
-  "price": {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "title": "Price"
-  },
-  "symbol": {
-    "title": "Symbol",
-    "type": "string"
-  },
-  "volume_24h": {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "title": "Volume 24H"
-  }
-}
    • removedOutput schema / properties / prices / items / required
      Removed value: -[
-  "id",
-  "symbol",
-  "price",
-  "market_cap",
-  "volume_24h",
-  "change_24h_pct"
-]
    • removedOutput schema / properties / prices / items / title
      Removed value: -"TokenPriceEntry"
    • removedOutput schema / properties / prices / items / type
      Removed value: -"object"
  2. Changed1 schema field changed
    • addedOutput schema / properties / prices / items / properties / fully_diluted_valuation
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Fully Diluted Valuation"
+}
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only provide readOnlyHint true. The description goes beyond by explaining unknown symbol auto-resolution against 'the full CoinGecko coin list', the unsupported nature of 'Bare 0x contract addresses', and the batch cap. These are meaningful behavioral details not present in the annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Six sentences, each carrying specific information: purpose, accepted input forms, resolution behavior, batch limit, address limitation, and reuse guidance. No filler or redundant phrasing; the main purpose is front-loaded.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return-value documentation is unnecessary. The description covers input flexibility, resolution behavior, batch constraints, and a reuse recommendation, making it comprehensive for a token-price lookup tool. There are no obvious missing behavioral expectations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with parameter descriptions already present, so the baseline is 3. The description adds value by revealing that full token names are accepted and that unknown symbols resolve automatically, which the schema does not mention. This enriches parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states 'Get current price, 24h change, market cap, fully-diluted valuation, and volume for one or more crypto tokens' — a specific verb and resource, clearly distinguishing it from siblings like get_token_price_historical by emphasizing 'current'. The tool's scope is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs 'If get_wallet_portfolio already returned price_usd/value_usd for a held token, reuse that value instead of calling get_token_price again', providing a clear when-not-to-use alternative. It also spells out accepted identifier types (symbols, names, CoinGecko IDs) and the 50-token batch limit, offering concrete selection guidance.

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

All Teardrop toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation3/5

Most tools target distinct data sources, but several near-duplicates exist: get_token_approvals/get_wallet_approvals, get_defi_positions/get_wallet_positions, and get_wallet_portfolio/get_eth_balance. The descriptions do cross-reference and clarify the differences, so an agent can disambiguate with effort, but names alone are not enough.

Naming Consistency4/5

The dominant get_<noun> pattern is clear and nearly all names use lowercase snake_case with verb-first conventions. A few tools like calculate, record_predictions, http_fetch, and web_search break the get_ pattern, but the overall style remains predictable.

Tool Count2/5

34 tools is excessive for a single server, even for a broad DeFi/onchain analytics domain. The count is inflated by generic utilities such as calculate, count_text_stats, web_search, and http_fetch, plus multiple overlapping data-retrieval endpoints, making the surface hard to scan.

Completeness4/5

The set covers an unusually wide range of domain operations: prices, balances, portfolio/positions, approvals, yields, TVL, DEX quotes/volume, transactions, blocks, gas, ENS, contract reads, and risk assessments. It is view-only by design, so missing write/transaction tools is acceptable; minor gaps like address-based token pricing or transaction simulation are workaround-able.

Resources