Skip to main content
Glama
Sign In

cryptofeed402

by site.cryptofeed402
OverviewDiscussionsAdmin

OHLCV candles (paid, x402) — $0.003

get_candles
Read-onlyIdempotent

Paid endpoint ($0.003): OHLCV candles for any Hyperliquid perp (venue=hyperliquid, default; main dex + HIP-3; intervals 1m,3m,5m,15m,30m,1h,2h,4h,8h,12h,1d,3d,1w,1M; limit 1-500, default 100; optional end= epoch ms or ISO for older candles, Hyperliquid keeps the most recent 5000 per interval) or any OKX USDT spot pair (venue=okx; intervals 1m-12h,1d,1w,1M; limit 1-300; most recent only). Bad params or unknown symbol return an error and no charge. Returns the x402 payment requirements and URL. Free sample response: https://cryptofeed402.site/samples/candles

Input Schema

NameRequiredDescriptionDefault
endNoHyperliquid only: end time, epoch ms or YYYY-MM-DD / ISO 8601 UTC
limitNoDefault 100; max 300 for okx
venueNo
symbolYesHyperliquid perp ticker, e.g. BTC, ETH, kPEPE; HIP-3 builder-dex perps as dex:TICKER, e.g. xyz:TSLA; for venue=okx a spot base ticker, e.g. PEPE
intervalNoDefault 1h. 3d/8h are Hyperliquid only, 6h is OKX only

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "interval": "1h",
+    "limit": 100,
+    "symbol": "BTC"
+  }
+]
    • addedInput schema / properties / interval / examples
      Added value: +[
+  "1h"
+]
    • addedInput schema / properties / limit / examples
      Added value: +[
+  100
+]
    • addedInput schema / properties / symbol / examples
      Added value: +[
+  "BTC"
+]
  2. Added

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses the $0.003 cost, x402 payment requirements, no-charge behavior on bad params or unknown symbols, and Hyperliquid's most-recent-5000-per-interval retention. These are material operational traits an agent needs before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is front-loaded and every detail is relevant, but it is delivered as one very dense sentence with nested parentheticals. It is informative yet not optimally scannable or structurally clean.

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 no output schema, the description carries the return-value burden and does so: it states that the endpoint returns x402 payment requirements and a URL, and it links to a free sample response. Combined with venue and error behavior, this is complete enough for correct invocation.

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?

With 80% schema coverage, the baseline is 3, but the description adds useful semantics: venue=hyperliquid is default, HIP-3 builder-dex symbols use dex:TICKER, end is Hyperliquid-only, and OKX is most-recent-only. It mostly complements rather than merely repeats the schema.

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 a specific resource and scope: OHLCV candles for Hyperliquid perps or OKX USDT spot pairs. It does not explicitly distinguish itself from siblings like get_price or get_spot, so it falls short of the top score for sibling differentiation.

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?

It gives clear usage context: venue defaults, interval availability by venue, limit ranges, optional end time for older Hyperliquid candles, and error/no-charge behavior. It stops short of naming when to use this instead of sibling tools or when not to use it.

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

All cryptofeed402 toolsInspect
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