Bitview

Historical price

get_historical_price

Read-onlyIdempotent

Completed four-hour BTC/USD closes, newest first as mempool.space lists them, labeled by interval end, from the first priced interval (2010-08-16). With a UNIX timestamp, returns the latest nonempty completed close at or before it; before the first close returns an empty list. The current partial interval is excluded. USD only (currency accepts USD); exchangeRates is empty.

Mempool.space docs

REST operation: GET /api/v1/historical-price.

Input Schema

Name	Required	Description	Default
`currency`	No	Quote currency: USD, the only one served
`timestamp`	No	UNIX timestamp: the latest close at or before it

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 30, 2026

addedInput schema / $defs / Currency

Added value: +{
+  "description": "A quote currency prices are served in: USD only.",
+  "enum": [
+    "USD"
+  ],
+  "type": "string"
+}

changedInput schema / $defs / Timestamp / description

Previous value: -"UNIX timestamp in seconds"New value: +"A Unix timestamp, in seconds."

removedInput schema / $defs / Timestamp / format
```
Removed value: -"uint32"
```

addedInput schema / properties / currency

Added value: +{
+  "$ref": "#/$defs/Currency",
+  "description": "Quote currency: USD, the only one served"
+}

addedInput schema / properties / timestamp / description

Added value: +"UNIX timestamp: the latest close at or before it"

removedOutput schema / $defs / Dollars / format
```
Removed value: -"double"
```
addedOutput schema / $defs / ExchangeRates / additionalProperties
```
Added value: +false
```

changedOutput schema / $defs / HistoricalPrice / properties / prices / items / $ref

Previous value: -"#/$defs/HistoricalPriceEntry"New value: +"#/$defs/PricePoint"

removedOutput schema / $defs / HistoricalPriceEntry

Removed value: -{
-  "properties": {
-    "USD": {
-      "allOf": [
-        {
-          "$ref": "#/$defs/Dollars"
-        }
-      ]
-    },
-    "time": {
-      "allOf": [
-        {
-          "$ref": "#/$defs/Timestamp"
-        }
-      ]
-    }
-  },
-  "required": [
-    "time",
-    "USD"
-  ],
-  "type": "object"
-}

addedOutput schema / $defs / PricePoint

Added value: +{
+  "properties": {
+    "USD": {
+      "allOf": [
+        {
+          "$ref": "#/$defs/Dollars"
+        }
+      ]
+    },
+    "time": {
+      "allOf": [
+        {
+          "$ref": "#/$defs/Timestamp"
+        }
+      ]
+    }
+  },
+  "required": [
+    "time",
+    "USD"
+  ],
+  "type": "object"
+}

removedOutput schema / $defs / Timestamp / format
```
Removed value: -"uint32"
```

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Adds real behavior beyond the readOnly/idempotent annotations: ordering (newest first), labeling convention (interval end), exclusion of the current partial interval, empty-list edge case, and that exchangeRates comes back empty. These are exactly the non-obvious traits an agent would otherwise have to discover by trial.

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?

Front-loaded with the core resource and ordering, then edge cases, then docs link and REST operation. Dense and mostly waste-free, though the opening sentence packs several clauses and the repeated 'USD only' point sits slightly awkwardly after the empty-list caveat.

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, the description need not explain return shape, and it covers everything else an agent needs: scope, ordering, timestamp resolution, boundary behavior, and the currency limitation. No material gaps for a two-param read.

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%, so the baseline is 3; the description earns a step above by spelling out the timestamp semantics on boundary cases (nonempty completed close at or before it, empty list before inception) and restating the USD-only constraint beyond the enum.

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+resource with granularity: 'Completed four-hour BTC/USD closes ... labeled by interval end, from the first priced interval (2010-08-16).' An agent can tell this is the historical 4h close series rather than a spot quote, though the nearest sibling (get_prices) is never named to make the split explicit.

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?

Gives concrete selection conditions: with no timestamp it lists all closes newest-first, with a UNIX timestamp it returns the latest close at or before it, and before the first close it returns an empty list. It does not name or exclude the sibling price/series tools, so routing is inferred rather than stated.

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

All Bitview 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.