Skip to main content
Glama
the-staq

TradeStaq MCP

Official

list_top_traders

Browse a leaderboard of top-performing traders to copy. Filter by time period and sort by ROI, PnL, or win rate.

Instructions

Browse the leaderboard of top-performing traders you can copy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of traders to return (max 50)
periodNoLeaderboard time period30d
sortByNoSort criteriaroi
Behavior3/5

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

No annotations are provided, so the description must convey behavioral traits. It states 'Browse,' indicating a read-only operation, and provides no hints of destructive actions or auth requirements. The description is adequate but does not fully disclose scope or side effects, earning a mid-range score.

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 conveys the core functionality without any unnecessary words. It is well-structured and immediately understandable.

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?

Given the simplicity of the tool (3 optional parameters, no output schema), the description is nearly complete. It clearly communicates the overall function. However, it could briefly mention the returned data structure or the nature of the leaderboard, but this is a minor gap.

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?

The input schema covers 100% of parameters with descriptions, so the description adds no additional meaning beyond the schema. The tool's description does not elaborate on parameter usage beyond what is already in the schema, resulting in a baseline score of 3.

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 clearly states the tool's purpose: to browse a leaderboard of top-performing traders for copying. It uses specific verbs ('Browse') and resource ('leaderboard of top-performing traders'), and implicitly distinguishes from sibling tools like 'list_bots' or 'list_exchanges'.

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 for finding traders to copy but does not explicitly state when to use this tool vs. alternatives (e.g., 'search_markets' or 'follow_trader'). No exclusions or prerequisites are mentioned. It meets the minimum viability but lacks explicit guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/the-staq/tradestaq-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server