Skip to main content
Glama
Sign In

Highwire

by fun.highwire
OverviewDiscussionsAdmin

Get creator fees

get_creator_fees
Read-onlyIdempotent

What a creator wallet's higher.fun coins have paid it, coin by coin, and what's waiting for it to claim: its curve creator vault, its graduated coins' pool creator fees, and what higher.fun owes it off-chain. The same numbers as highwire.fun/fees/creator/. To claim, use build_claim_creator_fees.

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": {
      "wallet": "<wallet>"
    },
    "name": "get_creator_fees"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesA Solana wallet address (base58).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real context: the data spans three distinct sources including off-chain obligations, and claiming requires a separate mutating tool. It also grounds the output in the public web view highwire.fun/fees/creator/<wallet>, telling the agent results should match that page.

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?

Two sentences, both front-loaded with the payoff (what has been paid / what is claimable) and the alternative action last. The opening clause is slightly dense and grammatically tangled ('What a creator wallet's higher.fun coins have paid it'), but no sentence is wasted.

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?

With no output schema and a single required parameter, the description does the necessary work by enumerating the three return categories and pointing to the claim path. Complete enough to call correctly, though it does not describe the shape or units of the returned figures.

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 base58 Solana address pattern and format already documented in the schema, so the baseline is 3. The description adds only the qualifier that the wallet is interpreted as a *creator* wallet whose earnings are being reported.

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 names a specific subject (a creator wallet's earned and unclaimed higher.fun fees) and enumerates the three buckets returned: curve creator vault, graduated-coin pool creator fees, and off-chain amounts. It is clearly distinct from generic fee tools in scope, though it never explicitly contrasts itself with siblings like get_coin_fees or get_ecosystem_fees.

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?

It gives a clear trigger-to-action mapping by pointing at build_claim_creator_fees for the claim step, implicitly framing this tool as the read-only status check. It stops short of stating when *not* to use it (e.g., use get_coin_fees for per-coin fee data instead of per-wallet).

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

All Highwire toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources