Skip to main content
Glama
Sign In
Highwire

Highwire

by HigherMaestro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get leaderboard

get_leaderboard
Read-onlyIdempotent

Retrieve higher.fun leading traders or creators over the last 24 hours or 7 days to spot active market participants.

Instructions

higher.fun's top traders or top creators 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_leaderboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNotraders
windowNo24h

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the content scope (traders vs creators, 24h vs 7d) but does not explain how ranking is determined or what the response includes, which is a modest additional gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single compact sentence fragment with no wasted words, and the core scoping information is front-loaded. Nothing irrelevant is included.

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 simple two-enum-parameter tool with no output schema, the description is adequate but not complete. It says what the leaderboard covers, but does not mention the ranking metric or any result-structure expectations, leaving a small but meaningful gap for an agent invoking it.

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

Parameters4/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 parameter meaning. It does map both parameters well in natural language: 'top traders or top creators' corresponds to kind, and 'last 24 hours or 7 days' corresponds to window, covering both enum dimensions without leaving an agent guessing.

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 states the exact resource (leaderboard), the two leaderboard types (top traders or top creators), and the two time windows (24h or 7d). It is clear enough to distinguish this from siblings like get_top_coins, though it is phrased as a fragment rather than a full verb-led sentence.

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 explicit guidance is given about when to use this tool versus alternatives, nor any exclusions. The intended use is implied by the purpose statement, but an agent receives no help deciding between this and sibling tools such as get_top_coins or get_coin_holders.

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

Deploy Server

Other Tools