get_scheduleGet the F1 season race calendar. Provide year (e.g., 2024). Returns all rounds with race name, circuit, location, and date.
| Name | Required | Description | Default |
|---|---|---|---|
| season | Yes | Season year (e.g., "2025") |
| Name | Required | Description | Default |
|---|---|---|---|
| total | Yes | Total number of races in season | |
| season | Yes | F1 season year | |
| schedule | Yes | List of races |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / examplesAdded value: +[
+ {
+ "season": "2025"
+ },
+ {
+ "season": "2024"
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "schedule": {
+ "description": "List of races",
+ "items": {
+ "properties": {
+ "circuit_id": {
+ "description": "Ergast circuit ID",
+ "type": "string"
+ },
+ "circuit_name": {
+ "description": "Circuit name",
+ "type": "string"
+ },
+ "country": {
+ "description": "Country of circuit",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "date": {
+ "description": "Race date (ISO format)",
+ "type": "string"
+ },
+ "locality": {
+ "description": "City/locality of circuit",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "name": {
+ "description": "Race name",
+ "type": "string"
+ },
+ "round": {
+ "description": "Round number",
+ "type": "integer"
+ },
+ "season": {
+ "description": "F1 season year",
+ "type": "string"
+ },
+ "time": {
+ "description": "Race start time",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "season",
+ "round",
+ "name",
+ "circuit_id",
+ "circuit_name",
+ "locality",
+ "country",
+ "date",
+ "time"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "season": {
+ "description": "F1 season year",
+ "type": "string"
+ },
+ "total": {
+ "description": "Total number of races in season",
+ "type": "integer"
+ }
+ },
+ "required": [
+ "season",
+ "total",
+ "schedule"
+ ],
+ "type": "object"
+}Input schema / examplesRemoved value: -[
- {}
-]Output schema / (root)Previous value: -{
- "properties": {
- "current_date": {
- "description": "Current date",
- "type": [
- "string",
- "null"
- ]
- },
- "games": {
- "items": {
- "properties": {
- "away_team": {
- "description": "Away team name or abbreviation",
- "type": [
- "string",
- "null"
- ]
- },
- "date": {
- "description": "Game date",
- "type": [
- "string",
- "null"
- ]
- },
- "home_team": {
- "description": "Home team name or abbreviation",
- "type": [
- "string",
- "null"
- ]
- },
- "id": {
- "description": "Game ID",
- "type": [
- "number",
- "null"
- ]
- },
- "start_time_utc": {
- "description": "Start time in UTC",
- "type": [
- "string",
- "null"
- ]
- },
- "state": {
- "description": "Game state",
- "type": [
- "string",
- "null"
- ]
- },
- "venue": {
- "description": "Venue name",
- "type": [
- "string",
- "null"
- ]
- }
- },
- "type": "object"
- },
- "type": "array"
- },
- "total_games": {
- "description": "Total number of games in schedule",
- "type": "number"
- }
- },
- "required": [
- "current_date",
- "total_games",
- "games"
- ],
- "type": "object"
-}New value: +nullOutput schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "current_date": {
+ "description": "Current date",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "games": {
+ "items": {
+ "properties": {
+ "away_team": {
+ "description": "Away team name or abbreviation",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "date": {
+ "description": "Game date",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "home_team": {
+ "description": "Home team name or abbreviation",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "id": {
+ "description": "Game ID",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "start_time_utc": {
+ "description": "Start time in UTC",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "state": {
+ "description": "Game state",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "venue": {
+ "description": "Venue name",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "total_games": {
+ "description": "Total number of games in schedule",
+ "type": "number"
+ }
+ },
+ "required": [
+ "current_date",
+ "total_games",
+ "games"
+ ],
+ "type": "object"
+}Input schema / examplesAdded value: +[
+ {}
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds detail about the return contents (race name, circuit, etc.), enhancing transparency.
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 sentences, front-loaded with action, no wasted words. Efficiently conveys all necessary information.
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?
Output schema exists, so return values are covered. The description mentions key output fields, making it complete for a simple calendar lookup tool.
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 100% with a clear description. The description reinforces the parameter with example values, adding practical guidance 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?
The description clearly states the action ('Get') and the specific resource ('F1 season race calendar'). It distinguishes from sibling tools, which are unrelated to F1 schedules.
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?
Provides example year usage and implies when to use this tool. Lacks explicit when-not-to-use or alternative tools, but context makes it clear.
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 have detailed 'use when' guidance and the polymarket/entity clusters are distinguishable, but ask_pipeworx and ask_pipeworx_beta are currently identical, and ask_pipeworx/ask_pipeworx_grounded/deep_research sit close together. Many other tools (ai_visibility_check vs scan_competitor_ai_presence, bet_research vs polymarket_edges) require careful reading to keep separate.
Consistent snake_case and recognizable subfamilies (ask_pipeworx*, polymarket_*, get_*) keep names readable. However the overall set mixes verb_noun (get_schedule, resolve_entity), bare verbs (remember, forget), noun phrases (recent_alerts, pipeworx_trending), and compound noun names (bet_research, polymarket_fill_risk), so there is no single predictable convention.
35 tools is well over the 25+ threshold and spans many unrelated concerns: F1 data, universal data lookup, prediction markets, subscriptions, memory, npm scanning, and AI visibility. While a broad data platform can justify a large surface, the mix of one-off and meta tools makes this feel bloated rather than well-scoped.
For a server named F1 the surface is thin: it covers schedule, driver profiles, race results, and driver standings but lacks constructor standings, qualifying, team/circuit data, and a driver list. The surrounding Pipeworx tools provide depth in other domains, but they do not fill the F1-specific gaps.