Skip to main content
Glama
Sign In

cryptofeed402

by site.cryptofeed402
OverviewDiscussionsAdmin

Coin lookup (paid, x402) — $0.0025

get_price
Read-onlyIdempotent

Paid endpoint ($0.0025): perp mark, funding, OI (Hyperliquid) plus OKX spot for any listed Hyperliquid perp (main dex or HIP-3 like xyz:TSLA; HIP-3 has no spot cross-check). Unknown symbols return an error and no charge. Returns the x402 payment requirements and URL; pay with your own x402 client. Free sample response: https://cryptofeed402.site/samples/price

Input Schema

NameRequiredDescriptionDefault
symbolYesHyperliquid perp ticker, e.g. BTC, ETH, kPEPE; HIP-3 builder-dex perps as dex:TICKER, e.g. xyz:TSLA

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "symbol": "BTC"
+  }
+]
    • addedInput schema / properties / symbol / examples
      Added value: +[
+  "BTC"
+]
  2. Changed3 schema fields changed
    • addedInput schema / properties / symbol / description
      Added value: +"Hyperliquid perp ticker, e.g. BTC, ETH, kPEPE; HIP-3 builder-dex perps as dex:TICKER, e.g. xyz:TSLA"
    • removedInput schema / properties / symbol / enum
      Removed value: -[
-  "BTC",
-  "ETH",
-  "SOL",
-  "HYPE",
-  "NEAR",
-  "AAVE"
-]
    • addedInput schema / properties / symbol / pattern
      Added value: +"^(?:[A-Za-z]{1,10}:)?[A-Za-z0-9]{1,20}$"
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover safety and idempotency, and the description adds meaningful behavioral context beyond them: the $0.0025 cost, the x402 payment flow, the fact that unknown symbols are not charged, and a sample response URL. This is exactly the extra operational detail an agent needs for a paid endpoint.

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

Conciseness4/5

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

The description is a dense but front-loaded paragraph that covers cost, data fields, symbol scope, error behavior, and payment flow without filler. It could be split for readability, but every clause carries information.

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 no output schema, the description lists the returned data categories and points to an external sample response URL, which is largely sufficient. It does not fully describe the response shape, but the sample link compensates for that gap.

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?

Schema coverage is 100%, so the single symbol parameter is already documented with pattern and examples. The description still adds semantic value by clarifying that HIP-3 builder-dex perps use the dex:TICKER format and have no spot cross-check, which goes beyond the schema text.

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 and resource: it returns perp mark, funding, OI, and OKX spot for any listed Hyperliquid perp. It distinguishes its scope from siblings like get_spot and get_perps by naming HIP-3 builder-dex symbols and the no-spot-cross-check caveat.

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 clearly explains the paid x402 context and that callers must pay with their own x402 client, plus that unknown symbols return an error and incur no charge. It does not explicitly route to alternatives such as get_spot or get_pricing, but the usage context is otherwise clear.

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