Skip to main content
Glama

Surf Market

surf_market
Read-only

Access crypto market data: token rankings, derivatives, ETF flows, liquidations, technical indicators, on-chain metrics, and the Fear & Greed Index.

Instructions

Use this when the user needs market data from Surf. Get a high-level view of the crypto market. Browse token rankings by market cap or volume, track derivatives across all exchanges, monitor spot ETF fund flows, view liquidation events, compute technical indicators (RSI, MACD, Bollinger Bands, and more), explore on-chain valuation metrics (NUPL, MVRV, SOPR), and check the Fear & Greed Index.

Commands: etf - ETF Flow History params: symbol* (string) [BTC, ETH, XRP, SOL, HYPE], sort_by (string) [flow_usd, timestamp], order (string) [asc, desc], from (string), to (string) exchange-flow-exchanges - Exchange Flow Exchanges params: symbol* (string) [BTC, ETH], limit (integer), offset (integer) fear-greed - Fear & Greed Index History params: from (string), to (string) futures - Futures Market Overview params: sort_by (string) [open_interest, funding_rate, volume_24h, long_short_ratio], order (string) [asc, desc] liquidation-chart - Liquidation Chart params: symbol* (string), interval (string), exchange (string), limit (integer), from (string), to (string) liquidation-exchange-list - Liquidation by Exchange params: symbol (string), time_range (string) [1h, 4h, 12h, 24h], sort_by (string) [liquidation_usd, long_liquidation_usd, short_liquidation_usd], order (string) [asc, desc] liquidation-order - Large Liquidation Orders params: exchange (string), symbol (string), min_amount (string), side (string) [long, short], sort_by (string) [usd_value, timestamp, price], order (string) [asc, desc], limit (integer), offset (integer), from (string), to (string) listing - Exchange Listing Events params: from* (string), to (string), symbol (string), exchange (string), product (string) [spot, margin, perp, pre_market_perp, all], type (string) [listing, delisting, cancelled, advanced, postponed], limit (integer), offset (integer) onchain-indicator - On-Chain Indicator params: symbol* (string) [BTC, ETH], metric* (string), granularity (string) [day], from (string), to (string), exchange (string) options - Options Market Data params: symbol* (string), sort_by (string) [open_interest, volume_24h], order (string) [asc, desc] price - Token Price History params: symbol* (string), time_range (string), from (string), to (string), currency (string) price-indicator - Technical Indicator params: indicator* (string), symbol* (string), interval (string), exchange (string) [binance, bybit, coinbase, kraken], from (string), to (string), options (string) public-sale - Public Sale / Crowdsale params: id (string), q (string) ranking - Token Rankings params: sort_by (string) [market_cap, change_24h, volume_24h], order (string) [asc, desc], category (string), limit (integer), offset (integer) tge - Token Generation Event params: id (string), q (string)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsNo
commandYes
Behavior3/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds context about the tool's scope and lists commands, but it does not disclose additional behaviors such as rate limits, pagination, response shapes, or error handling. It does not contradict the annotations, so a mid-level score is appropriate.

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 long but well-structured with a front-loaded purpose sentence and a consistent, readable format for the 15 commands. Each line adds necessary details (params, enums, required markers), though some redundancy exists (e.g., repeating 'string' everywhere). The length is justified by the tool's complexity, and it earns its place without being wasteful.

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 large number of subcommands (15) and the absence of both an output schema and detailed schema properties, the description provides a solid overview of capabilities and complete parameter lists. However, it does not describe the return format or data structure for individual commands, which is a notable gap since there is no output schema to clarify this. The overview partially addresses this, so a 4 is appropriate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema only defines a generic 'params' object with no properties, leaving 0% coverage. The description compensates thoroughly by listing every command with parameter names, required indicators (asterisk), enum values, and types. This is essential, high-value documentation that the schema completely lacks, making the tool usable.

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 opens with an explicit purpose: 'Use this when the user needs market data from Surf,' followed by a detailed enumeration of the data types it covers (rankings, derivatives, ETF flows, liquidations, technical indicators, on-chain metrics, Fear & Greed). This is a specific verb+resource+scope statement that clearly differentiates the tool from sibling tools focused on other domains like DEX, news, or wallets.

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?

The opening line provides general context ('Use this when the user needs market data'), but it does not explicitly mention when NOT to use it or suggest alternatives. Sibling tools such as surf_onchain, surf_exchange, and surf_token overlap in areas like on-chain indicators and exchange data, and the description does not clarify boundaries. The guidance is implied rather than explicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/asksurf-ai/surf-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server