Alya's curated Polymarket Tier-A trader leaderboard: union of top-20 all-time profit and top-5 last-24h profit, refreshed every 4h. Each row includes wallet, window (1d/all), rank, and lifetime USD profit. Use to construct your own copy-trading watchlist.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max rows (max 50) | |
| window | No | both |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full burden. It discloses the refresh rate (every 4h), the data composition (union of top-20 all-time and top-5 last-24h), and the output fields. This adequately informs the agent of the tool's behavior and output characteristics.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the core purpose, and every sentence adds essential information (purpose, composition, update frequency, output fields, use case). No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's low complexity (2 optional parameters, no output schema), the description fully covers the purpose, data behavior, output fields, and a use case. It is sufficient for an agent to understand and invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 50% (only limit described). The description adds value by explaining that the window parameter filters by time range (1d or all) and that 'both' combines them, which goes beyond the enum values. It does not elaborate further on limit, but the schema already covers its max constraint.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool provides a curated leaderboard of Polymarket Tier-A traders, specifying it is a union of top-20 all-time and top-5 last-24h profit, refreshed every 4h. It lists the output fields (wallet, window, rank, lifetime profit), distinguishing it from sibling tools like polymarket_edge or polymarket_signals.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly recommends using the tool to 'construct your own copy-trading watchlist', giving a clear use context. However, it does not provide exclusions or compare with alternative tools, so guidance on when not to use is missing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes and clear descriptions, but there is some potential confusion among the four Polymarket-related tools (categorize, edge, signals, top_traders) and among the multiple 'alya_' prefixed tools that query different data sources.
Naming patterns are mixed: some tools use 'alya_' prefix, others use action-based names like 'batch_calibrate' or 'image_gen', and YouTube tools all start with 'youtube_'. The inconsistency in prefixes and verb styles makes the set less predictable.
32 tools is high for an MCP server, and they span a wide, unrelated set of domains (Polymarket, YouTube, gemology, weather, earthquakes, health, celebrity, etc.), making the surface feel bloated and unfocused.
Each domain has incomplete coverage: Polymarket lacks trade execution, YouTube automation depends on external OAuth, health tools only offer diagnosis and drug interactions without follow-up, and other domains have minimal tooling. The server feels like a collection of one-off features rather than a coherent surface.