Skip to main content
Glama
Sports Hub MCP Server

Sports Hub MCP Server

by danmorris27

formulae: Get championships

formulae_get_championships
Read-onlyIdempotent

Lists Formula E championships by season with IDs and status, providing championship IDs needed to query standings.

Instructions

List Formula E championships (one per season, from 2014-15 to the current season) with their ids and status. The id (championshipId) feeds the standings tools.

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": "formulae_get_championships"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds that the result is one row per season across a defined historical window and includes an id and status, which is useful behavioral context in the absence of an output schema. Pagination or ordering behavior is not stated.

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 short sentences with zero filler: the first covers scope, coverage window, and returned fields; the second covers the downstream linkage. The most decision-relevant information is front-loaded.

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?

For a zero-required-param read tool with no output schema, the description supplies the season coverage, the identity of the returned key, and the reason to call it. What remains unstated — ordering, whether the list can be filtered, or that the full set is small enough to return unpaginated — is minor but would make it airtight.

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?

There is a single optional `fields` parameter and schema description coverage is 100%, so the schema already fully documents it. The description says nothing about `fields` (e.g., which keys are valid or what the default projection is), so it adds no meaning beyond the schema — 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?

The description gives a specific verb and resource ('List Formula E championships') plus granularity ('one per season, from 2014-15 to the current season') and returned fields ('ids and status'). Naming the series as Formula E distinguishes it from look-alike season tools such as f1_get_seasons or sportsdb_get_seasons, though no Formula E sibling (races, teams, standings) is contrasted by name.

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?

'The `id` (championshipId) feeds the standings tools' states the concrete downstream dependency, telling an agent to call this before formulae_get_driver_standings or formulae_get_team_standings. It never explicitly excludes alternatives or says when not to use it, so this is clear context rather than full routing guidance.

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