Crypto Bot Audit + Market Data (x402 paid)

Bitcoin spot price in fiat

market_btc_spot_prices

Read-onlyIdempotent

The reference BTC price in USD plus six other fiat currencies with the quote timestamp — as a Bitcoin-native explorer publishes it, not as a venue tape. Costs $0.001 USDC per call. Byte-identical to GET /market/btc-spot-prices?.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ts`	No
`aud`	No
`cad`	No
`chf`	No
`eur`	No
`gbp`	No
`jpy`	No
`usd`	No
`note`	No
`stale`	No
`caveat`	No
`reason`	No
`source`	No
`timeSec`	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": {
+    "aud": {
+      "type": "integer"
+    },
+    "cad": {
+      "type": "integer"
+    },
+    "caveat": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "chf": {
+      "type": "integer"
+    },
+    "eur": {
+      "type": "integer"
+    },
+    "gbp": {
+      "type": "integer"
+    },
+    "jpy": {
+      "type": "integer"
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "timeSec": {
+      "type": "integer"
+    },
+    "ts": {
+      "type": "string"
+    },
+    "usd": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

AddedSep 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds behavioral context beyond that: the per-call cost, the data source type (Bitcoin-native explorer vs. venue), and an exact endpoint equivalence ('Byte-identical to GET /market/btc-spot-prices?'). This is useful and does not contradict 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 sentences with no waste: the first front-loads the primary purpose and currency scope, the second gives a critical cost fact, and the third provides an exact API mapping. Every sentence earns its place, and the structure is highly scannable.

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, return-value details need not be in the description. The description covers purpose, cost, source distinction, and endpoint mapping. It does not enumerate the six fiat currencies, but that is likely in the output schema; omitting them is a minor gap rather than a completeness failure.

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?

The tool has zero parameters, so schema coverage is inherently complete. The description correctly omits parameter details since none exist, meeting the baseline for 0-param tools. No additional parameter semantics are needed.

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 verb-plus-resource: 'reference BTC price in USD plus six other fiat currencies with the quote timestamp.' It also explicitly contrasts with 'venue tape,' distinguishing it from exchange spot tickers. This makes the tool's purpose immediately clear and separable from siblings like market_kraken_ticker.

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 stating the data source ('as a Bitcoin-native explorer publishes it') and contrasts it with a venue tape, but it does not name alternative tools or give explicit when-to-use/when-not-to-use guidance. The cost mention ($0.001 USDC per call) adds a practical consideration, but selection guidance remains inferred rather than explicit.

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?