Crypto Bot Audit + Market Data (x402 paid)

Bitcoin USD price history

market_btc_usd_price_history

Read-onlyIdempotent

Daily BTC/USD closes back to the earliest point the explorer keeps, downsampled to a bounded number of points — a long-run price series without a key. Costs $0.001 USDC per call. Byte-identical to GET /market/btc-usd-price-history?timespan=6months&limit=20.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	points to return (newest first slice, max 500) (default 120)
`timespan`	No	history window (1month is rejected upstream and is therefore not offered) (default "6months")

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ts`	No
`name`	No
`note`	No
`unit`	No
`count`	No
`found`	No
`stale`	No
`total`	No
`caveat`	No
`reason`	No
`source`	No
`values`	No
`timespan`	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"
+      ]
+    },
+    "count": {
+      "type": "integer"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "name": {
+      "type": "string"
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "timespan": {
+      "type": "string"
+    },
+    "total": {
+      "type": "integer"
+    },
+    "ts": {
+      "type": "string"
+    },
+    "unit": {
+      "type": "string"
+    },
+    "values": {
+      "items": {},
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

AddedSep 24, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already mark it read-only, idempotent, and non-destructive. The description adds meaningful behavioral context: the $0.001 USDC cost, byte-identical equivalence to a specific GET endpoint, and downsampling to a bounded number of points. 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 two tight sentences with no filler: it front-loads the core purpose, then adds cost and exact endpoint equivalence. Every clause earns its place.

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?

Given the output schema, full parameter descriptions, and safety annotations, the description supplies the remaining operational facts an agent needs: cost, exact endpoint equivalence, and data-shaping behavior. Nothing essential is missing for correct invocation.

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?

Both parameters are fully documented in the schema, including limit defaults/max and timespan defaults plus the rejected 1month value. The description's mention of downsampling adds context, but the schema already carries the parameter semantics, so baseline 3 is appropriate.

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?

The description clearly states the resource (daily BTC/USD closes) and the operation (return a downsampled long-run price history back to the earliest point the explorer keeps). It is specific and understandable, though it does not explicitly contrast itself with sibling market_btc_* tools.

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 gives clear contextual guidance: this is for long-run daily price closes, not spot or intraday data. It does not explicitly name alternatives or say when not to use it, so it stops short of full routing guidance.

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?