Lists all available RaceHooks data feeds and the subscription tier each requires, including the synthetic events.race feed for structured race events.
List all available RaceHooks data feeds, including which subscription tier each feed requires. The special 'events.race' feed is a synthetic feed that emits structured events (overtakes, pit stops, safety cars, etc.) derived from multiple raw feeds.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It adds valuable behavioral context by explaining that 'events.race' is synthetic and emits structured events derived from multiple raw feeds, but it does not disclose pagination behavior, auth requirements, or what the response list contains beyond tiers.
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 efficient sentences with no filler. The core purpose is front-loaded, and the special synthetic-feed note follows as useful secondary context.
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 listing tool with no output schema and no annotations, the description covers the core purpose and the special feed semantics. It leaves gaps around the limit parameter and return behavior, so it is adequate but not complete.
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 only parameter is an optional limit, and schema description coverage is 0%. The description never mentions limit, pagination, or how many feeds are returned, so it does not compensate for the missing parameter documentation.
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?
States a specific verb and resource: list available RaceHooks data feeds, with the useful extra detail that subscription tier is included. The purpose is clear and effectively distinct from sibling tools, though it does not explicitly contrast itself with any related endpoint such as get_usage_by_feed or get_subscription.
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?
Usage is implied: an agent can infer this is the discovery tool for finding feeds and their required tiers. However, there is no explicit when-to-use guidance, no exclusions, and no named alternative for cases where the agent needs usage data or subscription details instead.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.