Crypto Bot Audit + Market Data (x402 paid)

Bitcoin hashrate and difficulty series

market_btc_mining_hashrate

Read-onlyIdempotent

Network hashrate points and the difficulty-adjustment series over a bounded window, with the current hashrate and difficulty the explorer reports. Costs $0.001 USDC per call. Byte-identical to GET /market/btc-mining-hashrate?window=1m&limit=20.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	points per series to return (max 400) (default 60)
`window`	No	history window (only the values measured) (default "1m")

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ts`	No
`note`	No
`found`	No
`stale`	No
`caveat`	No
`reason`	No
`source`	No
`window`	No
`hashrates`	No
`difficulty`	No
`hashratePoints`	No
`difficultyPoints`	No
`currentDifficulty`	No
`currentHashrateHs`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "caveat": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "currentDifficulty": {
+      "type": "number"
+    },
+    "currentHashrateHs": {
+      "type": "string"
+    },
+    "difficulty": {
+      "items": {},
+      "type": "array"
+    },
+    "difficultyPoints": {
+      "type": "integer"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "hashratePoints": {
+      "type": "integer"
+    },
+    "hashrates": {
+      "items": {},
+      "type": "array"
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "ts": {
+      "type": "string"
+    },
+    "window": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedSep 24, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive. The description adds a monetary cost per call ($0.001 USDC) and states the tool is byte-identical to a specific GET endpoint, which informs caching and reproducibility. This is valuable beyond structured 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?

Three short sentences, each carrying essential information: data scope, cost, and endpoint equivalence. No filler or redundancy. Structure front-loads the primary purpose.

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 an output schema present and full parameter documentation, the description is adequate for a read-only series tool. It covers purpose, cost, and endpoint mapping. Minor omissions like the meaning of 'bounded window' or 'difficulty-adjustment series' are not material given the targeted domain.

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 coverage is 100%, so the schema already documents limit and window with defaults and max values. The description adds a concrete example via the byte-identical endpoint expression ('?window=1m&limit=20'), reinforcing defaults, but adds no new semantic detail 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 states a specific resource: 'Network hashrate points and the difficulty-adjustment series' and clarifies that it returns current hashrate and difficulty from the explorer. This distinguishes it from sibling market tools that cover other Bitcoin metrics (e.g., fee estimates, spot prices). Though no sibling is named, the 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 Guidelines3/5

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

The description implies usage by naming the data returned (hashrate/difficulty) but does not explicitly state when to prefer this over sibling tools like market_btc_difficulty_adjustment. No exclusions or alternatives are mentioned. The 'bounded window' and endpoint equivalence provide some context, but an agent must infer the intended use.

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

All Crypto Bot Audit + Market Data (x402 paid) 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.

Resources

Need Help?