Highwire

Get ecosystem fees

get_ecosystem_fees

Read-onlyIdempotent

Retrieve fee totals paid by higher.fun coins, including creator, holder, platform, and pool allocations by phase and fee mode, plus claimable amounts, on-chain rates, and top coins.

Instructions

Every fee higher.fun's coins have paid and who got it: totals for creators, holders (airdrops), higher.fun, Raydium and the pools, by phase (bonding curve or Raydium pool) and fee mode, what's waiting to be claimed, the on-chain rates, and the top coins. The same numbers as highwire.fun/fees. Curve fees are measured on-chain; pool fees are computed from volume.

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_ecosystem_fees"
  }
}

Input Schema

Name	Required	Description	Default
`top`	No	How many coins to list, highest first.
`sort`	No	What to rank the coins by.	fees

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), so the description's real contribution is data-provenance: curve fees are measured on-chain while pool fees are computed from volume, which tells the agent the two numbers have different reliability. It also discloses that claimable-but-unclaimed amounts are included and that the figures mirror a public webpage, adding useful context beyond the annotations.

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?

It front-loads the core payload ('Every fee ... and who got it') before enumerating breakdowns, and every clause maps to a real part of the response, so nothing is filler. The middle section is a dense list-in-prose that takes a second read to parse, which costs it a point on structure.

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

Completeness5/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 carries the return-value burden — and it does: recipient totals, phase and fee-mode breakdowns, unclaimed amounts, on-chain rates, and the ranked coin list. Combined with fully documented parameters and complete safety annotations, an agent has everything needed to call and interpret this correctly.

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 100% — both 'top' (count, 1-100, default 20) and 'sort' (fees/volume/creator/higher enum) are fully documented in the schema. The description says 'the top coins' but adds nothing about ranking semantics, defaults, or how 'creator'/'higher' sorting behaves, so it matches the baseline rather than exceeding it.

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 gives a precise verb+resource: it returns aggregate fee totals across all higher.fun coins, broken out by recipient (creators, holders/airdrops, higher.fun, Raydium, pools), phase, and fee mode. The word 'ecosystem' plus 'Every fee higher.fun's coins have paid' distinguishes it from the per-coin get_coin_fees in intent, but it never names that sibling explicitly, leaving the boundary to inference.

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

Usage Guidelines3/5

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

Usage is only implied: 'the top coins' and the ranking work suggest a dashboard/analytics use case, and the reference to highwire.fun/fees hints at parity with a known page. There is no explicit statement of when to pick this over get_coin_fees, get_platform_info, or get_leaderboard, and no exclusions or prerequisites are given.

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