Skip to main content
Glama
lacausecrypto

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

f1: Get schedule

f1_get_schedule
Read-onlyIdempotent

Retrieve the Formula 1 race calendar for a season, including circuit details and race dates. Use it to plan race weekends or check upcoming Grand Prix events.

Instructions

Get the Formula 1 race schedule/calendar for a given season, including circuit info and race dates.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return (default 30, max 1000)
fieldsNoKeys to keep (comma-separated).
offsetNoNumber of results to skip for pagination
seasonNoSeason year (e.g. "2024") or "current" (default: "current")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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"
+}
    • removedInput schema / properties / offset / maximum
      Removed value: -9007199254740991
  2. Changed2 schema fields changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
  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, idempotentHint and openWorldHint, so the safety and repeatability profile is covered. The description adds useful content scope (circuit info and race dates) but says nothing about pagination behavior or how the default season resolves.

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?

A single front-loaded sentence with no filler; the verb, resource, scope and payload contents appear before any trailing clause. It is terse without being cryptic.

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 list tool whose annotations cover safety and whose schema covers all four parameters, the essentials are present, and the description partially compensates for the missing output schema by naming circuit info and race dates. It still omits ordering and pagination semantics, which an agent needs to page through a season correctly.

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 limit, offset, fields and season are already documented, including the "current" default. The description only implies the season filter and adds nothing about field projection or pagination interaction, so the baseline 3 applies.

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) and resource (Formula 1 race schedule/calendar) scoped to a season, plus what the payload contains (circuit info, race dates). The f1_ prefix cleanly separates it from the many *_get_schedule siblings, though it does not explicitly distinguish itself from f1 seasonal tools like f1_get_seasons or f1_get_circuits.

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?

No when-to-use guidance, no prerequisites, and no named alternatives. An agent must infer on its own that this is the calendar-level tool rather than f1_get_race_results or openf1_get_sessions, and that season supports "current" only by reading the schema.

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