Skip to main content
Glama

Surf Onchain

surf_onchain

Query blockchain data directly: look up transaction details by hash, check gas prices, and run structured or raw SQL queries across Ethereum, Base, Solana, and more.

Instructions

Use this when the user needs onchain data from Surf. Query blockchain data directly. Look up transaction details by hash, check gas prices, and run structured or raw SQL queries against indexed blockchain datasets spanning Ethereum, Base, Solana, and more.

Commands: bridge-ranking - Bridge Protocol Ranking params: time_range (string) [7d, 30d, 90d, 180d, 1y, all], limit (integer), offset (integer) dex-activity - DEX Protocol Activity params: chain* (string) [ethereum, base, bsc, arbitrum, tron], project (string), address (string), time_range (string) [1d, 7d, 30d, 90d], from (string), to (string), group_by (string) [total, day] gas-price - Current Gas Price params: chain* (string) structured-query - Blockchain Structured Query params: $schema (string), fields (array,null), filters (array,null), limit (integer), offset (integer), sort (array,null), source* (string) schema - On-Chain Table Schema params: table (string) sql - Blockchain SQL Query params: $schema (string), max_rows (integer), sql* (string) sql-job-create - Submit Asynchronous Blockchain SQL Job params: $schema (string), max_rows (integer), sql* (string) sql-job-get - Get Asynchronous Blockchain SQL Job params: job_id* (string) sql-job-results - Download Asynchronous Blockchain SQL Results params: job_id* (string), format (string) [json, csv] sql-preflight - Preflight Blockchain SQL Query params: $schema (string), max_rows (integer), sql* (string) tx - Transaction Details by Hash params: hash* (string), chain* (string), include (string) yield-ranking - Yield Pool Ranking params: project (string), sort_by (string) [apy, tvl_usd], order (string) [asc, desc], limit (integer), offset (integer)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsNo
commandYes
Behavior3/5

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

The annotations (readOnlyHint=false, etc.) offer minimal safety context. The description adds command-level detail but does not disclose potential side effects of SQL job submission or rate limits, nor does it specify that queries are read-only. This is adequate but not exemplary.

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 well-organized with a summary paragraph and a structured list of commands. It is relatively long due to 12 commands, but each line is terse and front-loaded with the usage directive. The structure aids quick scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (12 commands) and lack of output schema, the description covers the command inventory and parameter names/types but omits parameter meanings and return values. This leaves gaps for successful invocation without further research.

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 input schema is generic (command + params object), so the description carries the burden. It lists every command's parameters with types and some enums (e.g., chain options for dex-activity and gas-price), which is valuable. Yet many parameters like $schema or source are left unexplained, reducing full semantic clarity.

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 'Use this when the user needs onchain data from Surf' and elaborates with concrete capabilities like transaction hash lookups, gas prices, and SQL queries across Ethereum, Base, Solana, and more. This clearly distinguishes it from sibling tools focused on specific protocols or markets.

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 provides a clear 'Use this when' directive for onchain data needs and enumerates subcommands (e.g., gas-price, tx) for specific use cases. However, it does not explicitly contrast with sibling tools or state when not to use this tool, so it lacks the explicit when-not guidance that would merit a 5.

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