get_winnersRetrieve the top three podium finishers from recent weekly launch leaderboards, newest first, for Hall of Fame results. Specify up to 26 weeks to review.
Top 3 podium finishers from recent weeks, newest week first. These are the Hall of Fame entries on /winners.
| Name | Required | Description | Default |
|---|---|---|---|
| weeks | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful ordering and scope context ('newest week first', 'Hall of Fame entries'), which goes beyond annotations. It does not mention response format or edge cases, but those are less critical given the safety hints.
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?
Two tight sentences with no filler. The key facts—resource, ordering, and domain location—are front-loaded and every sentence contributes value.
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 one optional parameter and safety hints from annotations, the description covers the essential facts: what is returned, ordering, and domain context. It does not spell out the exact meaning of 'weeks', but the schema and context make it reasonably clear.
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?
The single parameter 'weeks' is not directly explained in the description, though the phrase 'from recent weeks' hints at it. The schema supplies defaults, min, and max, so an agent can infer basic semantics, but the description itself adds little direct parameter guidance.
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?
Description states a specific resource ('Top 3 podium finishers') and clear scope ('from recent weeks, newest week first'). It also grounds the resource ('Hall of Fame entries on /winners'), which helps distinguish it from sibling tools like get_weekly_leaderboard.
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?
No explicit guidance on when to use this tool versus alternatives such as get_weekly_leaderboard or get_launch_calendar. The description implies a retrieval use case but never states when this tool is preferred or when to avoid it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.