Agent Margin Router

Crypto OHLCV

crypto_ohlcv

Read-only

Historical OHLCV candles for any major crypto pair (Binance, Coinbase fallback): intervals 1m-1w, up to 500 candles, with period summary (high, low, volume, change %). Pay per call with USDC or USDT on Base via x402. 3 free calls per wallet.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Candles (1-500, default 100).
`quote`	No	Quote asset (default USDT).	USDT
`symbol`	Yes	Base asset, e.g. BTC.
`wallet`	No	Your EVM wallet address (0x...). Unlocks the free tier (3 free calls per wallet).
`api_key`	No	Optional AMR enterprise API key.
`interval`	No	1m 5m 15m 30m 1h 4h 1d 1w (default 1h).	1h
`x_payment`	No	Optional signed x402 payment payload (base64 JSON) for USDC/USDT on Base.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`quote`	Yes
`token`	No	Token actually used for payment (USDC, USDT or FREE).	USDC
`source`	Yes
`symbol`	Yes
`candles`	Yes
`routing`	Yes	How the request was routed (provider, fallback, cache, latency).
`summary`	Yes
`interval`	Yes
`cost_usdc`	Yes	Price charged in stablecoin units (USDC/USDT 1:1); 0 on the free tier.
`fetched_at`	No	UTC timestamp when the data was fetched.
`candle_count`	Yes
`freshness_seconds`	Yes	Age of the underlying data in seconds (0 = fetched live).
`x_payment_response`	No	Base64-encoded x402 settlement receipt (mirrors the X-PAYMENT-RESPONSE header). Only present when the call was paid with `x_payment`.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Response for ``POST /crypto-ohlcv``.",
+  "properties": {
+    "candle_count": {
+      "title": "Candle Count",
+      "type": "integer"
+    },
+    "candles": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "title": "Candles",
+      "type": "array"
+    },
+    "cost_usdc": {
+      "description": "Price charged in stablecoin units (USDC/USDT 1:1); 0 on the free tier.",
+      "title": "Cost Usdc",
+      "type": "number"
+    },
+    "fetched_at": {
+      "description": "UTC timestamp when the data was fetched.",
+      "format": "date-time",
+      "title": "Fetched At",
+      "type": "string"
+    },
+    "freshness_seconds": {
+      "description": "Age of the underlying data in seconds (0 = fetched live).",
+      "title": "Freshness Seconds",
+      "type": "integer"
+    },
+    "interval": {
+      "title": "Interval",
+      "type": "string"
+    },
+    "quote": {
+      "title": "Quote",
+      "type": "string"
+    },
+    "routing": {
+      "description": "How the request was routed (provider, fallback, cache, latency).",
+      "properties": {
+        "cache_hit": {
+          "default": false,
+          "description": "True if the result was served from cache.",
+          "title": "Cache Hit",
+          "type": "boolean"
+        },
+        "fallback_used": {
+          "default": false,
+          "description": "True if the primary provider failed and a fallback served the result.",
+          "title": "Fallback Used",
+          "type": "boolean"
+        },
+        "latency_ms": {
+          "default": 0,
+          "description": "End-to-end routing latency in milliseconds.",
+          "title": "Latency Ms",
+          "type": "integer"
+        },
+        "provider": {
+          "description": "Name of the upstream provider that served the result.",
+          "title": "Provider",
+          "type": "string"
+        },
+        "providers_tried": {
+          "description": "Providers attempted, in order.",
+          "items": {
+            "type": "string"
+          },
+          "title": "Providers Tried",
+          "type": "array"
+        }
+      },
+      "required": [
+        "provider"
+      ],
+      "title": "RoutingMeta",
+      "type": "object"
+    },
+    "source": {
+      "title": "Source",
+      "type": "string"
+    },
+    "summary": {
+      "additionalProperties": true,
+      "title": "Summary",
+      "type": "object"
+    },
+    "symbol": {
+      "title": "Symbol",
+      "type": "string"
+    },
+    "token": {
+      "default": "USDC",
+      "description": "Token actually used for payment (USDC, USDT or FREE).",
+      "title": "Token",
+      "type": "string"
+    },
+    "x_payment_response": {
+      "description": "Base64-encoded x402 settlement receipt (mirrors the X-PAYMENT-RESPONSE header). Only present when the call was paid with `x_payment`.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "freshness_seconds",
+    "cost_usdc",
+    "routing",
+    "symbol",
+    "quote",
+    "interval",
+    "candles",
+    "candle_count",
+    "summary",
+    "source"
+  ],
+  "type": "object"
+}

Changed6 schema fields changedSep 13, 2026
- addedInput schema / properties / interval / default
```
Added value: +"1h"
```
- addedInput schema / properties / limit / default
```
Added value: +100
```
- addedInput schema / properties / limit / maximum
```
Added value: +500
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- addedInput schema / properties / quote / default
```
Added value: +"USDT"
```
- changedInput schema / properties / wallet / description
```
Previous value: -"Your EVM wallet address (0x...). Unlocks the free tier (3 calls per wallet)."New value: +"Your EVM wallet address (0x...). Unlocks the free tier (3 free calls per wallet)."
```
AddedSep 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description adds substantial behavioral context: payment per call via x402, free-tier limits per wallet, data source fallback behavior, and the period summary. It does not detail rate limits or error behavior, but what is disclosed goes well beyond the 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 a single sentence that packs the essential facts—data scope, intervals, limit, summary, payment model, and free tier—without redundancy. It is front-loaded with the core purpose and keeps every clause informative.

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?

Given the output schema exists, the description correctly avoids repeating return values and instead covers data source, supported intervals, candle limits, payment method, and free calls. It leaves some room for ambiguity around 'major' pairs and exact pricing, but overall an agent has sufficient context to invoke the tool 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?

The input schema covers all 7 parameters with descriptions, so the baseline is 3. The tool description adds high-level context like 'any major crypto pair' and payment behavior, but it does not clarify individual parameters beyond what the schema already provides. This is acceptable given complete schema coverage.

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 'Historical OHLCV candles' for crypto pairs Brief, names data sources (Binance, Coinbase fallback), and specifies intervals, limit, and summary output. This differentiates it from current-price siblings like token_price or dex_price by emphasizing the historical candle-based nature.

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 clearly states this is for historical OHLCV data, which sets appropriate context for when to use it, but it does not explicitly mention alternatives or when not to use it. The 'historical' qualifier and candles-focused phrasing give enough context to distinguish from real-time price tools, though explicit exclusions are absent.

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

All Agent Margin Router 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.