Crypto Bot Audit + Market Data (x402 paid)

Bitfinex spot ticker

market_bfex_ticker

Read-onlyIdempotent

Top of book, last, 24h change in price and percent, and 24h volume/high/low for one Bitfinex spot pair. Costs $0.001 USDC per call. Byte-identical to GET /market/bfex-ticker?pair=BTCUSD.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`pair`	Yes	Bitfinex currency pair without the venue's leading t: BTCUSD, ETHUSD, ADAUSD [required]

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ts`	No
`ask`	No
`bid`	No
`last`	No
`note`	No
`pair`	No
`found`	No
`stale`	No
`caveat`	No
`low24h`	No
`reason`	No
`source`	No
`askSize`	No
`bidSize`	No
`high24h`	No
`change24h`	No
`volume24h`	No
`changePct24h`	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": {
+    "ask": {
+      "type": "integer"
+    },
+    "askSize": {
+      "type": "number"
+    },
+    "bid": {
+      "type": "integer"
+    },
+    "bidSize": {
+      "type": "number"
+    },
+    "caveat": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "change24h": {
+      "type": "integer"
+    },
+    "changePct24h": {
+      "type": "number"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "high24h": {
+      "type": "integer"
+    },
+    "last": {
+      "type": "integer"
+    },
+    "low24h": {
+      "type": "integer"
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "pair": {
+      "type": "string"
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "ts": {
+      "type": "string"
+    },
+    "volume24h": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

AddedSep 24, 2026

TDQS

A4.3/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 behavior. The description adds valuable context beyond annotations: a $0.001 USDC per-call cost and byte-identical equivalence to the REST endpoint, plus top-of-book semantics.

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?

Two focused sentences front-load the returned data and then state cost and endpoint equivalence. No filler or redundancy; every clause adds useful 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?

For a one-parameter read-only tool with a rich output schema, the description covers the data content, cost, exact endpoint behavior, and spot-pair scope. Nothing needed for correct invocation is missing.

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?

The single pair parameter has 100% schema description coverage, including examples and requirement. The description's endpoint example merely restates the pair query and adds no new formatting or semantic details 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 specifies the resource: top-of-book and 24-hour statistics for one Bitfinex spot pair. It distinguishes this from sibling tools by naming Bitfinex, spot, and single-pair scope, unlike market_bfex_candles or market_bfex_pairs.

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 states the exact use context: retrieving a ticker for one Bitfinex spot pair, and gives the REST-equivalent URL. It does not explicitly enumerate when not to use it or compare alternatives, but the venue, market type, and single-pair scope make the intended use clear.

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?