Skip to main content
Glama

Bitview

by io.github.bitcoinresearchkit
OverviewDiscussionsAdmin

Current BTC price

get_prices
Read-onlyIdempotent

Returns bitcoin latest price (on-chain derived, USD only).

Mempool.space docs

REST operation: GET /api/v1/prices.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedOutput schema / $defs / Dollars / format
      Removed value: -"double"
    • 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 / Prices
      Removed 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"
    • changedOutput schema / $ref
      Previous value: -"#/$defs/Prices"New value: +"#/$defs/PricePoint"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: the price is on-chain derived rather than an exchange feed, and only USD is supported, which materially affects interpretation of the result.

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?

Lead sentence front-loads what matters (what it returns, how it is derived, currency limit). The docs link and the REST operation line are mildly redundant but act as grounding metadata; nothing is padded.

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

Completeness4/5

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

With zero inputs, a present output schema, and full annotation coverage, the description only needs to convey meaning and constraints, which it does. Only the missing routing versus get_historical_price keeps it from a 5.

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?

Zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It correctly does not invent parameter discussion and instead spends its words on output meaning and constraints.

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?

States a specific verb and resource ('Returns bitcoin latest price') plus a meaningful qualifier ('on-chain derived, USD only'). The word 'latest' implicitly separates it from the sibling get_historical_price, so an agent can distinguish it without opening the schema.

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

Usage Guidelines3/5

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

Usage is only implied by the word 'latest' and the USD/on-chain constraint; there is no explicit statement of when to prefer this over get_historical_price. The agent can infer the split, but the description never names the alternative or sets the condition.

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

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