Skip to main content
Glama
lacausecrypto

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

openf1: Get sessions

openf1_get_sessions
Read-onlyIdempotent

Retrieve Formula 1 sessions by year, country, circuit, or session type to find practice, qualifying, sprint, or race schedules and details.

Instructions

List Formula 1 sessions. A session is a single on-track period such as a practice, qualifying, sprint, or race.

Input Schema

NameRequiredDescriptionDefault
yearNoSeason year (e.g. 2024)
fieldsNoKeys to keep (comma-separated).
session_keyNoUnique session identifier
country_nameNoCountry name (e.g. 'Italy', 'United Kingdom')
session_nameNoSession name (e.g. 'Race', 'Qualifying', 'Sprint', 'Practice 1')
session_typeNoSession type (e.g. 'Race', 'Qualifying', 'Practice')
circuit_short_nameNoShort circuit name (e.g. 'Monza', 'Silverstone')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "Keys to keep (comma-separated).",
+  "type": "string"
+}
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.2.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, and openWorld, so safety is covered. Beyond that the description adds only a definition of 'session' and discloses nothing about filtering behavior, result ordering, or how session_key interacts with the other filters.

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?

Two short sentences, front-loaded with the action, and the definitional second sentence earns its place by disambiguating 'session' across a large multi-sport tool set. No waste.

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

Completeness3/5

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

For a 7-parameter, zero-required, no-output-schema tool, the description omits the key fact that results can be narrowed by year, circuit, country, or session key, leaving the agent to discover filtering only from the schema. Adequate but with a clear gap.

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 all 7 parameters are already documented in the schema. The description adds no parameter meaning of its own, which is the expected baseline 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 description states a specific verb ('List') and resource ('Formula 1 sessions') and defines what a session is, which helps separate it from sibling data tools like openf1_get_drivers or openf1_get_laps. It does not explicitly distinguish itself from adjacent tools such as f1_get_schedule or motogp_get_sessions, 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 Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites, and no naming of alternatives despite a crowded sibling set of session/schedule tools. The description says nothing about the filtering use cases (by year, circuit, country) that define most real invocations.

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

Deploy Server

Other Tools