list_eventsMotocross races and events: Supercross, Pro Motocross nationals, Arenacross, amateur races and practice days. Filter by state, month or type.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | race, practice, national or supercross | |
| limit | No | Max results, default 25 | |
| month | No | YYYY-MM | |
| state | No | Two-letter US state code | |
| series | No | One series by its exact name, e.g. AMA Supercross, AMA Pro Motocross, Arenacross, GT Arenacross, ThrottleCross |
Changes observed during successful MCP inspections.
Input schema / properties / seriesAdded value: +{
+ "description": "One series by its exact name, e.g. AMA Supercross, AMA Pro Motocross, Arenacross, GT Arenacross, ThrottleCross",
+ "type": "string"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds domain scope (which event categories appear) but says nothing about result ordering, whether past events are included, or pagination behavior beyond the schema's limit field. Some added value, but thin against the annotated baseline.
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 short sentences with no filler, and the domain scope is front-loaded before the filtering hint. The first sentence is a noun phrase rather than a verb phrase, which slightly weakens front-loading of the action.
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?
All parameters are documented in the schema and the annotations carry the read-only profile, so an agent has enough to call the tool. However, with no output schema, the description should indicate what a returned event looks like at a high level (name, date, location) or whether results span future events only; that gap leaves it merely adequate.
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 description coverage is 100%, so all five parameters including the series enum example are already documented in structured form. The description echoes state, month, and type but adds no syntax or behavioral detail (e.g., how month interacts with recurring events, or whether series and type are mutually exclusive). Baseline 3 applies.
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 names the resource domain (motocross races and events) and enumerates concrete subtypes: Supercross, Pro Motocross nationals, Arenacross, amateur races, practice days. This is more specific than the title and lets an agent know this is an event catalog rather than a track lookup. It does not explicitly contrast with the similarly named sibling list_season_schedules, so it stops short of a 5.
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?
"Filter by state, month or type" implies how to use the tool but never states when to choose it over get_season_schedule or list_season_schedules, nor any when-not conditions. The usage context is inferable from the domain vocabulary rather than explicit.
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.