Highwire

List coins

list_coins

Read-onlyIdempotent

Retrieve higher.fun coins sorted by trending, new, market cap, or graduating status to research launches and monitor the Solana launchpad market. Paginate results with a cursor and set a limit.

Instructions

List higher.fun coins. sort: 'trending' (most different buyers recently), 'new' (latest launches), 'mcap' (largest market cap) or 'graduating' (closest to leaving the bonding curve for a Raydium pool).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_coins"
  }
}

Input Schema

Name	Required	Description	Default
`sort`	No		trending
`limit`	No
`cursor`	No	Pass nextCursor from the previous page to get the next one.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds no further behavioral context such as pagination behavior, result freshness, or result-set shape; its enum explanations are parameter semantics rather than behavioral disclosure.

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?

A single compact sentence with the resource stated first and the sort options enumerated compactly in parentheses. It is front-loaded and free of filler, though the nested parenthetical list is slightly dense.

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?

There is no output schema, so the description would ideally indicate what a coin entry contains or at least that results are paginated. Pagination is only inferable from the cursor field, and no return-value information is given, leaving a notable gap for a discovery tool.

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

Parameters3/5

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

Schema coverage is 33%: only cursor carries a schema description. The description compensates meaningfully for the sort enum by defining what each mode ranks on (recent distinct buyers, latest launches, market cap, distance to Raydium graduation). It says nothing about limit or its 1-50 bounds, leaving partial coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ("List higher.fun coins") and immediately enumerates the sort modes, so the agent knows it is a browsing/listing tool. It does not differentiate itself from siblings like get_top_coins, search_coins, or get_featured_coin, which also surface coins.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of when to prefer search_coins, get_top_coins, or get_coin instead. The agent must infer from the tool name and sort options that this is for unfiltered discovery.

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