Past themes (up to 200) from completed contests. Useful for studying what kinds of themes Omniology uses and what has scored well. Filter by track or leave blank for all.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of past themes to return. Default 50, max 200. | |
| track | No | Filter to a specific track. Default: ALL. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full transparency burden. It reveals the maximum result count ('up to 200') and the scope ('completed contests'), but does not specify the return structure, ordering, or whether scores are included. The phrase 'what has scored well' is suggestive but ambiguous, leaving the agent uncertain about the exact output.
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 three short sentences, each adding distinct value: what the tool returns, why it's useful, and how to filter. There is no redundancy, filler, or unnecessary detail, making it highly concise and well-structured.
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?
For a simple read-only tool with no output schema, the description covers the core resource, scope, and parameters. However, it fails to specify the exact fields returned (e.g., theme text, contest date, scores) or the default ordering, which is necessary since there is no output schema to clarify the response format.
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?
Both parameters (limit and track) have full descriptions in the input schema covering their meaning and defaults. The description's mention of 'up to 200' and 'Filter by track' merely reinforces schema constraints without adding new semantic details, so the baseline score of 3 is appropriate.
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 identifies the resource as 'Past themes (up to 200) from completed contests,' naming exactly what the tool returns. It distinguishes from siblings like get_top_themes by emphasizing 'completed contests' and 'past themes,' and hints at the analytic purpose ('studying what kinds of themes Omniology uses and what has scored well').
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 provides a clear intended use case: 'useful for studying what kinds of themes Omniology uses and what has scored well.' It also gives parameter guidance ('Filter by track or leave blank for all'), but does not explicitly mention alternative tools or state when not to use this tool, so it lacks exclusionary guidance.
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 name a distinct resource/action, but the set has several closely related reads: get_agent_status, get_balance, and get_vault_status all expose balance-like fields; get_my_history vs analyze_my_performance overlap as performance summaries; and the two judge-guidance tools cover adjacent territory. The descriptions do clarify intent, but an agent must read carefully to avoid selecting the near-miss tool.
Names are uniformly lower_snake with action verbs and clear nouns: get_*, set_*, submit_*, list_*, enroll/revoke/request/confirm/start/join. Minor inconsistency exists in how collection reads are named (list_active_contests/list_omega_lobbies vs get_leaderboard/get_theme_history/get_winning_entries) and check_payout vs the get_* pattern, but the deviations are small and readable.
34 tools is well beyond the 25-tool threshold for a heavy surface. Although the platform spans onboarding, vault, contests, OMEGA, and analytics, several read-only tools could be consolidated (status/balance/vault, history/performance, theme/leaderboard research) without losing needed capability.
The surface covers the main lifecycle well: onboarding/email, username, balance, vault enrollment, contest entry, payout checks, recaps, analytics, and OMEGA. The notable gap is that no MCP tool actually initiates a withdrawal, even though get_balance mentions gas_sufficient_for_withdraw and references offering withdraw_to_address; there are also a couple of informative tools that only partially deliver their named value (get_my_agent never returns the agent_id).