Skip to main content
Glama
lacausecrypto

Sports Hub MCP Server

f1_get_qualifying

Retrieve Formula 1 qualifying results including Q1, Q2, and Q3 lap times for any season and round.

Instructions

Get Formula 1 qualifying results. Returns Q1/Q2/Q3 times for drivers in a specific qualifying session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seasonNoSeason year (e.g. "2024") or "current" (default: "current")
roundNoRound number within the season
limitNoMaximum number of results to return (default 30, max 1000)
offsetNoNumber of results to skip for pagination
Behavior3/5

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

No annotations provided, so description carries full burden. It mentions return values (Q1/Q2/Q3 times) but doesn't disclose read-only nature, rate limits, or pagination behavior beyond parameter hints. Adequate but not rich.

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 sentences, no fluff, directly conveys purpose and output. Perfectly concise.

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?

Tool is simple with no output schema. Description adequately covers what the tool returns. However, lacks guidance on typical usage patterns (e.g., using season and round together). Slight gap for completeness.

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 descriptions already cover all 4 parameters (100% coverage). Description adds context about return values but does not enhance parameter understanding beyond schema. Baseline 3 is appropriate.

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?

Explicitly states it gets Formula 1 qualifying results and specifies the return includes Q1/Q2/Q3 times. Clearly differentiates from sibling tools like f1_get_race_results.

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?

Implies usage for qualifying sessions but provides no explicit guidance on when to use versus alternatives, nor any exclusions. Sibling tools are numerous but not referenced.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lacausecrypto/mcp-sports-hub'

If you have feedback or need assistance with the MCP directory API, please join our Discord server