mcp-server

Historical rates

get_rate_history

Read-onlyIdempotent

Historical rate timeseries for a symbol. Recent history (~30 days) is per-tick; older history is daily granularity. Depth is clamped to your plan (up to 365 days on Pro) and bounded by how far back data has been recorded. (Current plan: up to 1825 days of history.)

Input Schema

TableJSON Schema

Name	Required	Description
`days`	No	Days of history. Clamped server-side to your plan (Free 7, Starter 30, Growth 90, Pro 365, Enterprise 1825) and bounded by available data. Points within ~30 days are per-tick; older points are daily.
`symbol`	Yes	Coin symbol, case-insensitive
`provider`	No	Provider slug to scope to, case-insensitive

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

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

Changed2 schema fields changedJul 27, 2026

changedInput schema / properties / provider / description

Previous value: -"Provider slug to scope to"New value: +"Provider slug to scope to, case-insensitive"

changedInput schema / properties / symbol / description

Previous value: -"Coin symbol"New value: +"Coin symbol, case-insensitive"

Changed1 schema field changedJul 17, 2026

changedInput schema / properties / days / description

Previous value: -"Days of history. Clamped to the plan limit (7 Free, 1825 Pro)."New value: +"Days of history. Clamped server-side to your plan (Free 7, Starter 30, Growth 90, Pro 365, Enterprise 1825) and bounded by available data. Points within ~30 days are per-tick; older points are daily."

Changed5 schema fields changedJun 17, 2026

addedOutput schema / properties / data

Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "count": {
+      "type": "number"
+    },
+    "history": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "category": {
+            "enum": [
+              "lending",
+              "borrowing",
+              "staking",
+              "price"
+            ],
+            "type": "string"
+          },
+          "coinId": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "createdAt": {
+            "type": "string"
+          },
+          "metadata": {
+            "anyOf": [
+              {
+                "additionalProperties": {},
+                "type": "object"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "provider": {
+            "type": "string"
+          },
+          "providerSymbol": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "rate": {
+            "type": "number"
+          },
+          "symbol": {
+            "type": "string"
+          },
+          "timestamp": {
+            "description": "ISO-8601 observation time (oldest → newest)",
+            "type": "string"
+          }
+        },
+        "required": [
+          "provider",
+          "symbol",
+          "category",
+          "rate",
+          "timestamp",
+          "createdAt",
+          "coinId"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "symbol": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "symbol",
+    "history",
+    "count"
+  ],
+  "type": "object"
+}

removedOutput schema / properties / points

Removed value: -{
-  "description": "Time-ordered rate observations (oldest → newest)",
-  "items": {
-    "additionalProperties": true,
-    "properties": {
-      "timestamp": {
-        "description": "ISO-8601 timestamp of the data point",
-        "type": "string"
-      },
-      "value": {
-        "description": "The recorded numeric value",
-        "type": "number"
-      }
-    },
-    "required": [
-      "timestamp",
-      "value"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

removedOutput schema / properties / provider
```
Removed value: -{
-  "type": "string"
-}
```

removedOutput schema / properties / symbol

Removed value: -{
-  "type": "string"
-}

changedOutput schema / required

Previous value: -[
-  "symbol",
-  "points"
-]New value: +[
+  "data"
+]

Changed1 schema field changedMay 21, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "points": {
+      "description": "Time-ordered rate observations (oldest → newest)",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "timestamp": {
+            "description": "ISO-8601 timestamp of the data point",
+            "type": "string"
+          },
+          "value": {
+            "description": "The recorded numeric value",
+            "type": "number"
+          }
+        },
+        "required": [
+          "timestamp",
+          "value"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "symbol": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "symbol",
+    "points"
+  ],
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations declare readOnly, openWorld, idempotent. Description adds that point density changes after ~30 days, depth clamped to plan, and bounded by data recording. No contradictions.

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?

Two sentences, front-loaded with core purpose, then key details about granularity and plan limits. Every sentence is valuable.

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?

Output schema exists (not shown). Description covers timeseries data, granularity, plan limits, and boundaries. Complete for a read-only historical data tool.

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 descriptions for all 3 parameters. The description adds meaningful context about days parameter behavior (granularity change, clamping) beyond the schema.

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 it provides historical rate timeseries for a symbol. It distinguishes granularity: recent ~30 days per-tick, older daily. It differentiates from siblings like get_price (current price) and get_rates by specifying timeseries with plan limits.

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

Usage Guidelines4/5

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

The description implies use for historical data and mentions plan clamping. It lacks explicit when-to-use vs alternatives, but given sibling names (e.g., get_price), the purpose is clear.

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

All mcp-server 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.9/5.0

Disambiguation5/5

Each tool targets a distinct aspect of cryptocurrency data: coin metadata, prices, rates (current, historical, changes), earn products, market summaries, stablecoin analysis, and symbol resolution. The detailed descriptions clearly differentiate even similar tools like get_price and get_price_by_symbol, or get_rates and list_earn_products.

Naming Consistency3/5

All names use snake_case, but conventions vary: some are verb_noun (get_coin, list_coins, resolve_symbol), some are noun_noun (coin_history, fear_greed_index, market_summary), and some include 'by' for parameters. This mix is readable but could be more consistent.

Tool Count5/5

With 21 tools, the server covers a broad domain of cryptocurrency data without being overwhelming. Each tool serves a clear purpose, and the count is appropriate for a comprehensive data API.

Completeness5/5

The tool set covers nearly all expected operations for a crypto data server: coin listing, metadata, prices, historical data, rates, yield products, market stats, top coins, stablecoin analysis, and symbol resolution. No obvious gaps are present for the stated focus on price, rate, and yield data.

Resources

Need Help?