Highwire

Get coin fees

get_coin_fees

Read-onlyIdempotent

Retrieve every fee line for a higher.fun coin and its Raydium pool, including recipients, measurement method, volume, holder airdrops, and unclaimed fees.

Instructions

One higher.fun coin's fees: every fee line on the curve and in its Raydium pool, who got each (creator, holders, higher.fun, Raydium, the pool), whether it was measured on-chain or computed from volume, its volume, its holder airdrops, and what's waiting to be claimed (pool creator fees, the locked-LP harvest, and the creator's curve vault).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mint": "<mint>"
    },
    "name": "get_coin_fees"
  }
}

Input Schema

Name	Required	Description	Default
`mint`	Yes	The coin's mint address (base58). higher.fun mints usually end in 'high'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare the tool as read-only, idempotent, open-world, and non-destructive. The description adds value by enumerating the fee data and claimable amounts returned, but it does not disclose any additional behavioral traits such as rate limits, authentication needs, or response size.

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 a single dense sentence that front-loads the core purpose before enumerating the detailed contents. It is efficient but could be more scannable if broken into structured elements.

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

Completeness4/5

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

For a read-only tool with no output schema and full parameter documentation, the description covers what data is returned comprehensively. It lacks only minor details like error behavior or pagination, which are not critical here.

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%, with the single mint parameter fully documented in the schema. The description adds no extra meaning beyond the schema, so the baseline score of 3 is appropriate.

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 explicitly states it returns one higher.fun coin's fee lines, including the source of each fee and what's claimable. It distinguishes itself from ecosystem-wide fee tools by scoping to a single coin, though it doesn't explicitly name a sibling alternative.

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?

The description implies usage by describing the returned data in detail, but it provides no explicit guidance on when to use this tool versus get_coin, get_ecosystem_fees, or build_claim_creator_fees. The context is inferable from the name and scope, but not stated.

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