Skip to main content
Glama

Crawlora MCP

openf1_weather

Read-only

List track weather samples for a session, returning rainfall, air and track temperature, humidity, pressure and wind readings. Use session_key plus a date_from/date_to window to keep the sample range small; a valid empty match returns count 0 and a live-session call returns 503. For finer queries, add repeatable filter= (operators >=, <=, =, >, <) to narrow by rainfall or track_temperature, e.g. filter=rainfall=1; repeated filters on one attribute are OR'ed and ranges are inclusive.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "openf1_weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNoRepeatable upstream filter expression written as <attribute><operator><value> with operators >=, <=, =, > and <. Repeated filters on the same attribute are OR'ed, ranges are inclusive, and unknown attributes or values are rejected before the upstream call.
date_toNoOptional sample upper bound; RFC3339 or YYYY-MM-DD.
rainfallNoOptional rainfall flag, 0 or 1.
date_fromNoOptional sample lower bound; RFC3339 or YYYY-MM-DD.
meeting_keyNoOptional positive meeting key, or latest.
session_keyNoOptional positive session key, or latest.
humidity_gteNoOptional inclusive minimum relative humidity percentage.
humidity_lteNoOptional inclusive maximum relative humidity percentage.
pressure_gteNoOptional inclusive minimum air pressure in mbar.
pressure_lteNoOptional inclusive maximum air pressure in mbar.
wind_speed_gteNoOptional inclusive minimum wind speed in m/s.
wind_speed_lteNoOptional inclusive maximum wind speed in m/s.
wind_direction_gteNoOptional inclusive minimum wind direction in degrees.
wind_direction_lteNoOptional inclusive maximum wind direction in degrees.
air_temperature_gteNoOptional inclusive minimum air temperature in Celsius.
air_temperature_lteNoOptional inclusive maximum air temperature in Celsius.
track_temperature_gteNoOptional inclusive minimum track temperature in Celsius.
track_temperature_lteNoOptional inclusive maximum track temperature in Celsius.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only and open-world behavior, and the description adds non-obvious traits: an empty match returns count 0, live-session calls return 503, and unknown filter attributes/values are rejected before the upstream call. Return-format details are omitted, but an output schema exists, so this is a solid addition.

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

Conciseness4/5

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

The description is front-loaded with purpose, then narrowing advice, then filter mechanics — a logical order for an agent assembling a call. The filter sentence is dense and partly redundant with the schema, but every clause carries usable information.

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?

Given 18 optional parameters, an output schema, and read-only annotations, the description covers purpose, scope narrowing, and error behavior adequately. It leaves unstated that session_key/meeting_key accept "latest" and says nothing about result limits or ordering, which are the remaining gaps.

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 coverage is 100%, so all 18 parameters are already documented, including the filter expression grammar and inclusive-range/OR semantics. The description largely restates the filter contract and adds only the example filter=rainfall=1; it does not explain things like the "latest" value accepted by session_key/meeting_key.

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 names a specific verb and resource ("List track weather samples for a session") and enumerates the returned measures (rainfall, air/track temperature, humidity, pressure, wind). An agent can distinguish this from openf1_car_data or openf1_laps without opening the schema.

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?

It gives concrete usage advice: pair session_key with a date_from/date_to window to keep the sample range small, and add repeatable filters only for finer queries. It also warns about the live-session 503 and empty-match count 0. It does not name an alternative for cross-session weather lookups, but no obvious sibling competes here.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources