Skip to main content
Glama
Sign In
Sports Hub MCP Server

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

openf1: Get weather

openf1_get_weather
Read-onlyIdempotent

Retrieve session weather data—air and track temperature, humidity, pressure, wind speed/direction, rainfall—by session key, with optional date and field filters.

Instructions

Get weather data for a session: air/track temperature, humidity, pressure, wind speed/direction, rainfall.

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).
date_gteNoStart datetime filter (ISO 8601)
date_lteNoEnd datetime filter (ISO 8601)
session_keyYesSession identifier (required)

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 readOnlyHint/openWorldHint/idempotentHint, so the safety profile is covered. The description adds essentially nothing behavioral beyond the metric list: no note on whether session_key is required, how date filtering behaves, sampling granularity, or return shape. For a read-only weather feed this is thin but not misleading.

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?

A single front-loaded sentence with zero filler: verb, resource, scope, then the returned metrics. Nothing is redundant or buried.

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?

There is no output schema, so enumerating the returned weather metrics is genuinely useful and covers the return surface. However, with no usage context and no mention of the required session_key or date-range filtering semantics, the definition is only minimally complete for correct invocation.

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 four parameters (fields, date_gte, date_lte, session_key) are already documented in the schema; baseline 3 applies. The description's enumerated metrics loosely correspond to what 'fields' can select, but it adds no syntax or format detail beyond the schema.

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?

States a specific verb ('Get') plus resource ('weather data for a session') and enumerates the exact metrics returned (air/track temperature, humidity, pressure, wind, rainfall). This clearly distinguishes it from the other openf1_* siblings (laps, positions, car_data, etc.), though it never names a sibling directly.

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?

The description gives no when-to-use guidance, no prerequisites, and no alternatives. It implies session-scoped retrieval via the phrasing 'for a session', but an agent gets no help deciding how this differs from openf1_get_sessions or openf1_get_car_data beyond the field list.

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