Teardrop

Get Token Price Historical

get_token_price_historical

Read-only

Get historical price data for crypto tokens over a specified time window (1–365 days). Returns period statistics (start, end, % change, high, low) plus a downsampled daily price series, plus high_30d (raw observation maximum), std_30d (population standard deviation of daily returns as a decimal), and dca_baseline_90d (weekly samples over the preceding 90 UTC days, excluding the latest observation). dca_baseline_90d_partial identifies incomplete history. Use for period comparisons (month-over-month, YTD), trend analysis, and price charts. Prefer over web_search for time-comparative financial queries. Pass stats_only=true when the daily series is unnecessary. These metrics are pre-computed and should not be re-derived with calculate.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No	Lookback window in days (1–365). 1=5-min granularity, 2-90=hourly, 91+=daily.
`tokens`	Yes	Token symbols or CoinGecko IDs (e.g. ['BTC', 'ETH']). Max 10 per call.
`stats_only`	No	If true, omit the daily price series and return period stats plus precomputed 30-day high/volatility and 90-day DCA baseline metrics.
`vs_currency`	No	Quote currency (usd, eur, gbp, btc, eth). Lowercase 3–10 letters.	usd

Output Schema

TableJSON Schema

Name	Required	Description	Default
`days`	Yes
`tokens`	Yes
`vs_currency`	Yes

Schema Changelog

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

Changed12 schema fields changedAug 14, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / days / title
```
Added value: +"Days"
```
addedInput schema / properties / stats_only / title
```
Added value: +"Stats Only"
```
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_price_historicalArguments"

addedOutput schema / $defs

Added value: +{
+  "DailyPricePoint": {
+    "properties": {
+      "date": {
+        "title": "Date",
+        "type": "string"
+      },
+      "price": {
+        "title": "Price",
+        "type": "number"
+      }
+    },
+    "required": [
+      "date",
+      "price"
+    ],
+    "title": "DailyPricePoint",
+    "type": "object"
+  },
+  "TokenHistoricalEntry": {
+    "properties": {
+      "daily_prices": {
+        "items": {
+          "$ref": "#/$defs/DailyPricePoint"
+        },
+        "title": "Daily Prices",
+        "type": "array"
+      },
+      "dca_baseline_90d": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Mean of weekly daily-close samples from the preceding 90 UTC days, in vs_currency.",
+        "title": "Dca Baseline 90D"
+      },
+      "dca_baseline_90d_partial": {
+        "anyOf": [
+          {
+            "type": "boolean"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "True when the DCA baseline uses incomplete 90-day history; null when unavailable.",
+        "title": "Dca Baseline 90D Partial"
+      },
+      "high_30d": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Maximum raw price observation in the trailing 30 UTC days, in vs_currency.",
+        "title": "High 30D"
+      },
+      "id": {
+        "title": "Id",
+        "type": "string"
+      },
+      "price_change_pct": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Price Change Pct"
+      },
+      "price_end": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Price End"
+      },
+      "price_high": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Price High"
+      },
+      "price_low": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Price Low"
+      },
+      "price_start": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Price Start"
+      },
+      "std_30d": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Population standard deviation of trailing 30-day simple daily returns, as a decimal.",
+        "title": "Std 30D"
+      },
+      "symbol": {
+        "title": "Symbol",
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "symbol",
+      "price_start",
+      "price_end",
+      "price_change_pct",
+      "price_high",
+      "price_low",
+      "daily_prices"
+    ],
+    "title": "TokenHistoricalEntry",
+    "type": "object"
+  }
+}

addedOutput schema / properties / tokens / items / $ref
```
Added value: +"#/$defs/TokenHistoricalEntry"
```

removedOutput schema / properties / tokens / items / properties

Removed value: -{
-  "daily_prices": {
-    "items": {
-      "properties": {
-        "date": {
-          "title": "Date",
-          "type": "string"
-        },
-        "price": {
-          "title": "Price",
-          "type": "number"
-        }
-      },
-      "required": [
-        "date",
-        "price"
-      ],
-      "title": "DailyPricePoint",
-      "type": "object"
-    },
-    "title": "Daily Prices",
-    "type": "array"
-  },
-  "dca_baseline_90d": {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "description": "Mean of weekly daily-close samples from the preceding 90 UTC days, in vs_currency.",
-    "title": "Dca Baseline 90D"
-  },
-  "dca_baseline_90d_partial": {
-    "anyOf": [
-      {
-        "type": "boolean"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "description": "True when the DCA baseline uses incomplete 90-day history; null when unavailable.",
-    "title": "Dca Baseline 90D Partial"
-  },
-  "high_30d": {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "description": "Maximum raw price observation in the trailing 30 UTC days, in vs_currency.",
-    "title": "High 30D"
-  },
-  "id": {
-    "title": "Id",
-    "type": "string"
-  },
-  "price_change_pct": {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "title": "Price Change Pct"
-  },
-  "price_end": {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "title": "Price End"
-  },
-  "price_high": {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "title": "Price High"
-  },
-  "price_low": {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "title": "Price Low"
-  },
-  "price_start": {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "title": "Price Start"
-  },
-  "std_30d": {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "description": "Population standard deviation of trailing 30-day simple daily returns, as a decimal.",
-    "title": "Std 30D"
-  },
-  "symbol": {
-    "title": "Symbol",
-    "type": "string"
-  }
-}

removedOutput schema / properties / tokens / items / required

Removed value: -[
-  "id",
-  "symbol",
-  "price_start",
-  "price_end",
-  "price_change_pct",
-  "price_high",
-  "price_low",
-  "daily_prices"
-]

removedOutput schema / properties / tokens / items / title
```
Removed value: -"TokenHistoricalEntry"
```
removedOutput schema / properties / tokens / items / type
```
Removed value: -"object"
```

Changed5 schema fields changedAug 9, 2026

changedInput schema / properties / stats_only / description

Previous value: -"If true, omit the daily price series and return only period stats (start/end/change/high/low) to reduce payload size."New value: +"If true, omit the daily price series and return period stats plus precomputed 30-day high/volatility and 90-day DCA baseline metrics."

addedOutput schema / properties / tokens / items / properties / dca_baseline_90d

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Mean of weekly daily-close samples from the preceding 90 UTC days, in vs_currency.",
+  "title": "Dca Baseline 90D"
+}

addedOutput schema / properties / tokens / items / properties / dca_baseline_90d_partial

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "True when the DCA baseline uses incomplete 90-day history; null when unavailable.",
+  "title": "Dca Baseline 90D Partial"
+}

addedOutput schema / properties / tokens / items / properties / high_30d

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Maximum raw price observation in the trailing 30 UTC days, in vs_currency.",
+  "title": "High 30D"
+}

addedOutput schema / properties / tokens / items / properties / std_30d

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Population standard deviation of trailing 30-day simple daily returns, as a decimal.",
+  "title": "Std 30D"
+}

First observedJul 9, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations declare readOnlyHint=true, but the description adds substantial context beyond that: it explains how dca_baseline_90d is computed (weekly samples over preceding 90 UTC days, excluding latest observation), notes dca_baseline_90d_partial identifies incomplete history, and warns that metrics are pre-computed and should not be re-derived with calculate. No contradiction with annotations.

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?

The description is front-loaded with the core purpose, then compactly enumerates return metrics and usage guidance. Every sentence serves a distinct function—purpose, output details, edge-case identifier, use cases, alternative, and optimization. No redundancy or filler.

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?

The tool is complex with multiple precomputed metrics, but the description covers all key aspects: return value composition, granularity caveats, partial history handling, and guidance on avoiding re-derivation. An output schema exists, so return values need not be exhaustively spelled out, yet the description still provides a rich overview.

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 baseline is 3. The description adds a small amount of semantic value by clarifying when stats_only is useful ('when the daily series is unnecessary'), but most parameter meaning is already fully documented in the schema. No significant gap to compensate.

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?

The description clearly states a specific verb+resource ('Get historical price data for crypto tokens') and details the exact outputs (period statistics, daily price series, high_30d, std_30d, dca_baseline_90d). It distinguishes from siblings like get_token_price and web_search by focusing on historical time windows and time-comparative analysis.

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?

Explicit use cases are given ('Use for period comparisons (month-over-month, YTD), trend analysis, and price charts'), with a direct alternative ('Prefer over web_search for time-comparative financial queries') and a conditional optimization ('Pass stats_only=true when the daily series is unnecessary'). This is textbook usage guidance.

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

All Teardrop tools Inspect

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

Need Help?