Skip to main content
Glama
Sign In
@thryx/mcp-server

@thryx/mcp-server

by lordbasilaiassistant-sudo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thryx_leaderboard

Discover top traders by volume and creators by fees earned. Choose a 24h, 7d, or 30d range to view rankings.

Instructions

Top traders by volume + top creators by fees earned. Range: 24h | 7d | 30d.

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

Input Schema

NameRequiredDescriptionDefault
rangeNoTime window.7d

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It does not state that this is a safe read-only operation, nor does it mention any side effects, permissions, or output format. The behavior is implied but not explicitly disclosed.

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 concise sentence that front-loads the key information (what is returned and the range options). Every word earns its place, with no filler or redundancy.

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 tool with one parameter and no output schema, the description explains the content and range but does not specify the response structure (e.g., whether traders and creators are separate lists, or how many entries are returned). It is adequate but leaves some ambiguity.

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 coverage is 100% with the 'range' parameter having an enum and description. The tool description repeats the range values but does not add new meaning beyond the schema. Baseline 3 is appropriate since the schema does the heavy lifting.

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 clearly states the tool returns top traders by volume and top creators by fees, which is a specific resource and metric. It distinguishes itself from siblings like thryx_trending (trending tokens) and thryx_stats_v2 (general stats) by focusing on user leaderboards. The absence of an explicit verb like 'list' or 'get' is a minor deduction.

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 guidance is given on when to use this tool versus alternatives. It does not mention exclusions or prerequisites. The description implies it is for leaderboard queries but does not differentiate from similar tools such as thryx_trending or thryx_stats_v2.

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