Crypto Bot Audit + Market Data (x402 paid)

Coinbase product specification

market_cbex_product_spec

Read-onlyIdempotent

The venue's own rules for one product: tick and lot size, minimum order, whether it is margin/post-only/limit-only, and whether trading is enabled. Costs $0.001 USDC per call. Byte-identical to GET /market/cbex-product-spec?product=BTC-USD.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`product`	Yes	Coinbase Exchange product id, BASE-QUOTE (BTC-USD, ETH-USD, SOL-USD) [required]

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`ts`	No
`base`	No
`note`	No
`found`	No
`quote`	No
`stale`	No
`caveat`	No
`reason`	No
`source`	No
`status`	No
`display`	No
`postOnly`	No
`limitOnly`	No
`cancelOnly`	No
`auctionMode`	No
`fxStablecoin`	No
`baseIncrement`	No
`marginEnabled`	No
`statusMessage`	No
`maxSlippagePct`	No
`minMarketFunds`	No
`quoteIncrement`	No
`highBidLimitPct`	No
`tradingDisabled`	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": {
+    "auctionMode": {
+      "type": "boolean"
+    },
+    "base": {
+      "type": "string"
+    },
+    "baseIncrement": {
+      "type": "string"
+    },
+    "cancelOnly": {
+      "type": "boolean"
+    },
+    "caveat": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "display": {
+      "type": "string"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "fxStablecoin": {
+      "type": "boolean"
+    },
+    "highBidLimitPct": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "limitOnly": {
+      "type": "boolean"
+    },
+    "marginEnabled": {
+      "type": "boolean"
+    },
+    "maxSlippagePct": {
+      "type": "string"
+    },
+    "minMarketFunds": {
+      "type": "string"
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "postOnly": {
+      "type": "boolean"
+    },
+    "quote": {
+      "type": "string"
+    },
+    "quoteIncrement": {
+      "type": "string"
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "status": {
+      "type": "string"
+    },
+    "statusMessage": {
+      "type": "string"
+    },
+    "tradingDisabled": {
+      "type": "boolean"
+    },
+    "ts": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedSep 24, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior. The description adds the per-call cost ($0.001 USDC) and byte-identical equivalence to a REST endpoint, which are valuable behavioral details not present in the annotations. No contradiction found.

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 with no filler: it front-loads what the tool returns, then states cost and exact API equivalence. Every sentence adds information.

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 a 100% documented parameter, an output schema, and rich annotations, the description covers the tool's purpose, contents, cost, and exactness. An agent has enough to select and call it correctly.

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% and the single "product" parameter has a clear description. The description minimally reinforces that the parameter selects a single product and mentions a BTC-USD example in the endpoint, but it does not add substantial semantics 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 clearly identifies the resource as "the venue's own rules for one product" and enumerates the exact contents (tick/lot size, minimum order, order type restrictions, trading enabled). This distinguishes it from market data siblings like market_cbex_ticker or market_cbex_candles because it is about product configuration, not current market state.

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 context is implied: an agent should call this when it needs the product specification for a Coinbase product. However, it does not provide explicit when-to-use versus alternatives, exclusions, or pointers to related tools such as market_cbex_ticker or other exchange spec tools.

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?