Retrieve Formula 1 race weekends for the current or a chosen season, including session schedules and status, and filter to upcoming events.
List F1 events (race weekends) for the current or a specific season, including session schedules and status.
| Name | Required | Description | Default |
|---|---|---|---|
| year | No | Season year, e.g. 2026. Defaults to current season. | |
| limit | No | ||
| upcoming | No | true = only return events that haven't started yet |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. 'List' implies a safe read and the sentence notes results include session schedules and status, but nothing is said about ordering, pagination (limit defaults to 30, max 50), or whether 'status' means live/upcoming/completed.
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?
A single front-loaded sentence with no filler; scope and payload contents come first. Slightly too terse to be fully informative, but nothing wasted.
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?
No output schema and no annotations, so the description should do more: it never explains what an event record contains beyond 'session schedules and status', nor how limit/pagination affects results. Adequate but with clear gaps for a list endpoint.
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 67%: year and upcoming are well documented in the schema, while limit is undocumented. The description's 'current or a specific season' merely echoes the year parameter and adds no format or edge-case detail beyond the schema.
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?
Specific verb+resource ('List F1 events (race weekends)') with clear scope (current or a specific season) and a hint at payload contents. It doesn't distinguish itself from nearby siblings like list_seasons, get_season_races, or get_race, which could plausibly return overlapping data.
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 'current or a specific season' phrasing implies when year should be set, but there is no explicit when-to-use/when-not guidance and no mention of when to pick list_seasons or get_season_races instead. Usage is inferred rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.