Skip to main content
Glama
Sign In
lacausecrypto

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

openf1: Get positions

openf1_get_positions
Read-onlyIdempotent

Retrieve Formula 1 session position and ranking data to track how driver positions change over time. Filter by session, driver, position, or fields.

Instructions

Get position/ranking data during a session. Shows how positions change over time.

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).
positionNoFilter by specific position (e.g. 1 for leader)
session_keyYesSession identifier (required)
driver_numberNoFilter by driver number

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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, so safety and idempotency are covered. The description adds one useful behavioral fact, that output is a time series ('how positions change over time'), but says nothing about ordering, granularity, or live-vs-final data.

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?

Two short sentences with the core purpose front-loaded and no filler. It is efficient, though the second sentence is close to restating the first rather than adding new information.

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 read-only, fully documented 4-param tool with no output schema, the description is minimally adequate. Annotations carry the safety profile, but the agent gets no sense of return shape (one row per driver per timestamp?) or of how to use the position/driver_number filters to narrow results.

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 explains fields, position, session_key, and driver_number. The description adds no filter syntax, range, or interpretation guidance beyond that, so the baseline 3 is appropriate.

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+resource ('Get position/ranking data') scoped to 'during a session', which separates it from siblings like openf1_get_intervals (gaps) and openf1_get_laps. It does not explicitly name an alternative sibling, but the resource is concrete enough to identify what the tool returns.

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 only usage signal is the implied 'during a session' scope, which mirrors the required session_key. There is no when-to-use guidance, no distinction from openf1_get_intervals or openf1_get_laps, and no note on when ranking data is preferable to other session data.

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