Skip to main content
Glama

Surf Search

surf_search
Read-only

Search across Surf's crypto data universe for projects, news, wallet addresses, web pages, funds, airdrops, and prediction markets using a single query.

Instructions

Use this when the user needs search data from Surf. Find anything across Surf's data universe. Search for crypto projects, news articles, wallet addresses, web pages, investment funds, airdrop opportunities, and prediction market events — all from a single unified search interface.

Commands: airdrop - Airdrop Search params: q (string), phase (string), reward_type (string) [airdrop, points, whitelist, nft, role, ambassador], task_type (string), has_open (boolean), sort_by (string) [total_raise, xscore, last_status_update], order (string) [asc, desc], limit (integer), offset (integer), include_tasks (boolean) airdrop-activities - Airdrop Activities params: limit (integer), offset (integer) events - Project Event Search params: id (string), q (string), type (string), limit (integer), offset (integer) fund - Fund Search params: q* (string), limit (integer), offset (integer) fundraising - Fundraising Event Search params: q (string), from (string), to (string), source (string) [social, news], lang (string) [en, zh, ja, kr], min_importance (integer), sort_by (string) [recency, relevance, importance], order (string) [asc, desc], limit (integer), offset (integer) news - News Article Search params: q* (string), limit (integer), offset (integer) prediction-market - Search Prediction Markets params: condition_id (string), market_ticker (string), platform (string) [polymarket, kalshi], category (string), status (string) [active, closed, finalized], sort_by (string) [volume_1d, volume_7d, volume_30d, open_interest, trade_count_7d, days_to_resolution], order (string) [asc, desc], smart_money (string) [bullish, bearish], q (string), limit (integer), offset (integer) project - Project Search params: q* (string), limit (integer), offset (integer) token - Token Symbol Resolution params: q* (string), chain (string), limit (integer), offset (integer) wallet - Wallet Search params: q* (string), limit (integer), offset (integer) web - Web Search params: q* (string), limit (integer), offset (integer), site (string), include_content (boolean)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsNo
commandYes
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the multi-command structure and per-command parameter details but does not provide additional behavioral context like pagination behavior, rate limits, or return format.

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 opens with a concise directive, then presents a structured command list. It is somewhat long due to the many subcommands, but the list format is efficient and each line carries necessary parameter information. Front-loading of the core purpose is good.

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?

For a multi-command search tool with no output schema, the description provides substantial detail: all commands, their parameters, and enums. However, it lacks information about return values, pagination defaults, or constraints like how 'params' object is interpreted. Given the complexity, it is fairly complete but not exhaustive.

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?

The schema only defines 'command' and a generic 'params' object, so description coverage is 0%. The description compensates by listing every command's specific parameters, including required markers (q*) and enums for several fields. It adds significant meaning beyond the schema, though it doesn't explain what each parameter semantically represents.

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 states the tool performs unified search across Surf's data universe, listing specific categories (crypto projects, news, wallets, etc.). This distinguishes it from domain-specific siblings like surf_news or surf_token.

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 explicitly says 'Use this when the user needs search data from Surf' and enumerates search types, giving clear context. However, it does not explicitly mention when not to use it or compare to specific sibling tools, so no exclusions are stated.

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