SportIQ

f1_get_sessions

Read-onlyIdempotent

Retrieve Formula 1 sessions for a championship year, filtering by country or session type, or get the most recently completed session.

Instructions

Return F1 sessions for a given year, optionally filtered by country or session name.

Args: year: Championship year (e.g. 2026). country: Optional country name to filter (e.g. "Netherlands"). session_name: Optional session name to keep, case-insensitive (e.g. "Race", "Qualifying", "Sprint"). latest_completed: When true, return only the single session that ended most recently (greatest date_end before now, UTC) — e.g. with session_name="Race", the latest finished Grand Prix.

Returns: data.sessions: list of session objects with session_key, session_type, date. meta.source: adapter that served the data.

Input Schema

Name	Required	Description
`year`	Yes	Championship year (e.g. 2026).
`country`	No	Optional country name to filter (e.g. "Netherlands").
`session_name`	No	Optional session name to keep, case-insensitive (e.g. "Race", "Qualifying", "Sprint").
`latest_completed`	No	When true, return only the single session that ended most recently (greatest date_end before now, UTC) — e.g. with session_name="Race", the latest finished Grand Prix.

Output Schema

Name	Required	Description	Default
`data`	No
`meta`	No
`error`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.4.0Oct 29, 2026

changedInput schema / properties / country / description

Previous value: -"Optional country name to filter (e.g. \"Monaco\")."New value: +"Optional country name to filter (e.g. \"Netherlands\")."

addedInput schema / properties / latest_completed

Added value: +{
+  "default": false,
+  "description": "When true, return only the single session that ended most recently (greatest date_end before now, UTC) — e.g. with session_name=\"Race\", the latest finished Grand Prix.",
+  "title": "Latest Completed",
+  "type": "boolean"
+}

addedInput schema / properties / session_name

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional session name to keep, case-insensitive (e.g. \"Race\", \"Qualifying\", \"Sprint\").",
+  "title": "Session Name"
+}

changedInput schema / properties / year / description

Previous value: -"Championship year (e.g. 2025)."New value: +"Championship year (e.g. 2026)."

First observedv0.3.1Jul 10, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description still adds real behavioral detail beyond them: filtering is case-insensitive, and latest_completed selects the greatest date_end strictly before now in UTC. The Returns section duplicates the output schema, which is minor redundancy rather than a gap.

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

Conciseness3/5

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

The opening sentence is well front-loaded and zero-waste, but the Args and Returns blocks are a docstring that repeats structured schema and output-schema content almost one-for-one. Those lines do not earn their place for an agent that already receives the schema.

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

Completeness4/5

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

This is a low-complexity lookup with four fully documented parameters, complete annotations, and an output schema, so the description does not need to explain return shapes. What is missing is only cross-tool routing guidance, e.g. that session keys obtained here feed f1_get_race_results or f1_get_lap_times.

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?

Schema description coverage is 100%, so the schema already documents all four parameters, and the Args block largely restates those same descriptions verbatim. The one marginal addition, case-insensitivity of session_name, also appears in the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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

Purpose4/5

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

The first sentence names a specific verb and resource (return F1 sessions) and states the required scope (a given year) plus the optional filters. It is distinguishable from siblings like f1_get_race_results or f1_get_drivers, but it does not explicitly contrast itself with them, 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.

Usage Guidelines3/5

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

The description explains how to narrow results via country, session_name, and latest_completed, including a concrete example ('with session_name="Race", the latest finished Grand Prix'). However, it never states when to use this tool versus alternatives such as f1_get_race_results, nor any prerequisites, so usage is only implied.

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

Deploy Server