Skip to main content
Glama

F1

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Race Results

get_race_results
Read-onlyIdempotent

Get race results for a specific F1 grand prix. Provide season year and round number (e.g., 2024, round 5). Returns finishing position, driver, constructor, status, and points.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roundYesRound number within the season (e.g., "1")
seasonYesSeason year (e.g., "2025")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesRace date (ISO format)
nameYesRace name
roundYesRace round number
seasonYesF1 season year
circuitYesCircuit name
resultsYesList of race results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / results / items / properties
      Previous value: -"[Object: undefined]"New value: +{
+  "code": {
+    "description": "Three-letter driver code",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "constructor": {
+    "description": "Constructor name",
+    "type": "string"
+  },
+  "driver_id": {
+    "description": "Ergast driver ID",
+    "type": "string"
+  },
+  "fastest_lap_time": {
+    "description": "Fastest lap time",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "grid": {
+    "description": "Starting grid position",
+    "type": "integer"
+  },
+  "laps": {
+    "description": "Laps completed",
+    "type": "integer"
+  },
+  "name": {
+    "description": "Full driver name",
+    "type": "string"
+  },
+  "number": {
+    "description": "Driver car number",
+    "type": "string"
+  },
+  "points": {
+    "description": "Points scored in race",
+    "type": "number"
+  },
+  "position": {
+    "description": "Finishing position",
+    "type": "integer"
+  },
+  "status": {
+    "description": "Race status (e.g., Finished, Retired)",
+    "type": "string"
+  },
+  "time": {
+    "description": "Race time (for finished)",
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "circuit": {
+      "description": "Circuit name",
+      "type": "string"
+    },
+    "date": {
+      "description": "Race date (ISO format)",
+      "type": "string"
+    },
+    "name": {
+      "description": "Race name",
+      "type": "string"
+    },
+    "results": {
+      "description": "List of race results",
+      "items": {
+        "properties": "[Object: undefined]",
+        "required": [
+          "position",
+          "number",
+          "driver_id",
+          "code",
+          "name",
+          "constructor",
+          "grid",
+          "laps",
+          "status",
+          "points",
+          "time",
+          "fastest_lap_time"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "round": {
+      "description": "Race round number",
+      "type": "integer"
+    },
+    "season": {
+      "description": "F1 season year",
+      "type": "string"
+    }
+  },
+  "required": [
+    "season",
+    "round",
+    "name",
+    "circuit",
+    "date",
+    "results"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "round": "5",
+    "season": "2024"
+  },
+  {
+    "round": "1",
+    "season": "2025"
+  }
+]
  4. First observed

TDQS

A4.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and nondestructive behavior, so the description does not need to restate safety. It adds output-field context, but does not disclose additional behavioral traits such as pagination, sorting, or data source limitations. This is acceptable given the strong annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two tight sentences that front-load the core purpose and then specify required inputs and return fields. Every sentence contributes useful information without redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, has only two fully documented parameters, given safety annotations, and an output schema exists. The description provides enough context for an agent to invoke it correctly without needing additional information about return values or side effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already fully describes both parameters with 100% coverage. The description adds a combined example ('2024, round 5') and clarifies the relationship between season and round, but this largely mirrors the schema descriptions rather than providing substantial new meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource — 'Get race results for a specific F1 grand prix' — and lists the returned fields (finishing position, driver, constructor, status, points). This clearly distinguishes it from siblings like get_current_standings, get_schedule, and get_driver.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear invocation context: provide season year and round number for a specific grand prix. It does not explicitly name alternatives or exclusion conditions, but the context is specific enough that an agent can infer when this tool is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All F1 toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources