Highwire

Get top coins

get_top_coins

Read-onlyIdempotent

Retrieve coins ranked by trading volume on higher.fun for 24-hour or 7-day windows.

Instructions

The coins with the most trading volume on higher.fun over the last 24 hours or 7 days.

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": "get_top_coins"
  }
}

Input Schema

Name	Required	Description	Default
`window`	No		24h

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuine behavioral context by disclosing the ranking metric (trading volume) and the two time windows, but it omits how many coins are returned, how they are ordered, and whether results are paginated or truncated.

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 short sentence with no filler or redundancy, and the key qualifiers (volume, time window, platform) are front-loaded. The only structural weakness is the missing verb, which makes it read as a label rather than a definition of an action.

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?

For a one-parameter read-only tool with no output schema and full annotation coverage, the description is close to sufficient, but it should still state that it returns a ranked list and roughly how many entries or what fields. An agent can call it correctly but cannot predict the shape or size of the response.

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 description coverage is 0%, so the description must carry the parameter meaning, and it does partially: 'over the last 24 hours or 7 days' maps directly onto the window enum values. However, it does not name the parameter, state the default (24h), or clarify that omitting it yields the 24h window.

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

Purpose3/5

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

The sentence names a specific resource and ranking metric (coins with the most trading volume on higher.fun), but it is a noun fragment with no verb, so it never states that the tool retrieves or returns a list. It also fails to distinguish itself from siblings like list_coins, get_leaderboard, or get_trade_tape, which an agent could easily confuse with this.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative is named. The only hint is the 24h/7d window, which implies a trending/volume-ranking use case, but the agent must infer that against list_coins and get_leaderboard on its own.

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