Skip to main content
Glama
Sports Hub MCP Server

Sports Hub MCP Server

by danmorris27

openliga: Get teams

openliga_get_teams
Read-onlyIdempotent

Retrieve the list of teams participating in a specified league and season to identify competitors and support sports data workflows.

Instructions

Get the list of teams participating in a league for a given season.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "league_shortcut": "<league_shortcut>",
      "season": "<season>"
    },
    "name": "openliga_get_teams"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).
seasonYesSeason year, e.g. '2023'
league_shortcutYesLeague shortcut, e.g. 'bl1'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

A3.5/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 profile is covered. The description adds only the league/season scoping constraint and nothing about return shape, list size, or whether teams are league-season specific.

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?

A single front-loaded sentence with zero filler. The resource and its scope are stated up front and every clause is necessary.

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 simple read tool with full schema coverage and safety annotations, the definition is minimum-viable. It omits what the returned team objects contain and whether results differ per season, which an agent might reasonably want.

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 league_shortcut, season and fields are each documented in the schema. The description restates the league and season concepts but adds no format or syntax detail (e.g. 'bl1', '2023') beyond what the schema already provides. Baseline 3.

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 and resource ('Get the list of teams') plus scope ('participating in a league for a given season'). Clear and distinguishable from the openliga match/table/scorer siblings, though it never names an alternative to contrast against.

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?

Usage is implied by 'for a given season' — an agent knows to call it when it has a league and season. There is no explicit when-to-use, when-not-to-use, or pointer to siblings like openliga_get_available_leagues to discover valid league shortcuts.

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