Skip to main content
Glama

Surf Token

surf_token
Read-only

Analyze token on-chain data: view top holders, transfer history, DEX trades, and unlock schedules.

Instructions

Use this when the user needs token data from Surf. Analyze individual tokens on-chain. Look up top holders and their share of supply, track ERC-20/SPL token transfers, browse DEX swap history, and view upcoming token unlock schedules with allocation breakdowns.

Commands: dex-trades - Token DEX Trade History params: address* (string), chain (string) [ethereum, base, bsc, arbitrum, tron], limit (integer), offset (integer), include (string) holders - Token Holders params: address* (string), chain* (string), limit (integer), offset (integer), include (string) tokenomics - Token Unlock Schedule params: id (string), symbol (string), from (string), to (string) transfer-counterparties - Top Transfer Counterparties params: address* (string), chain* (string) [ethereum, base, bsc, arbitrum, tron], direction* (string) [to, from], metric (string) [count, amount, amount_usd], time_range (string) [1d, 7d, 30d, 90d], limit (integer), offset (integer), include (string), exclude_labels (string) transfer-stats - Token Transfer Activity Summary params: address* (string), chain* (string) [ethereum, base, bsc, arbitrum, tron], time_range (string) [1d, 7d, 30d, 90d], include (string) transfers - Token Transfer History params: address* (string), chain* (string) [ethereum, base, solana, tron, bsc, arbitrum], from (string), to (string), limit (integer), offset (integer), include (string)

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 this as read-only and non-destructive. The description adds valuable detail about what operations can be performed (holders, transfers, DEX trades, tokenomics), but does not disclose anything beyond that, such as rate limits, pagination behavior, or response format. It adds some context but not deep behavioral transparency.

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 command headings and parameter lists, making it scannable. It front-loads the main use case and each section serves a purpose. Slight overhead from repeating chain lists across commands, but overall efficient for the tool's complexity.

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?

With no output schema, the description covers input parameters thoroughly but offers little about what outputs look like or how results are returned. It mentions the kind of data (top holders, transfer stats) but not structure or pagination details. For a multi-command tool, this leaves some gaps in completeness.

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 'command' and 'params' as generic objects with zero coverage. The description compensates fully by listing every available command and its parameters, including required markers, allowed enums for chain, direction, metric, and time_range, plus types. This is far beyond what the schema provides, making it highly informative.

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's purpose: 'Use this when the user needs token data from Surf.' It specifies exact capabilities like analyzing token holders, transfers, DEX trades, and token unlock schedules. This distinguishes it from sibling tools that focus on DEX, wallet, or market data.

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?

Provides an explicit 'when to use' statement in the first line. It does not explicitly mention when not to use it or name alternative tools, but the specific subcommands and scope make usage context clear. Lacks exclusionary guidance, hence not 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