Skip to main content
Glama
Sports Hub MCP Server

Sports Hub MCP Server

openliga: Get current matchday

openliga_get_current_matchday
Read-onlyIdempotent

Need a league's current matchday schedule? Retrieve all matches for that round by providing the league shortcut, e.g. 'bl1'.

Instructions

Get the matches for the current matchday of a league.

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>"
    },
    "name": "openliga_get_current_matchday"
  }
}

Input Schema

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

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

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 and repeatability profile is covered. The description adds no further behavioral context such as how 'current' is resolved or what happens outside an active season, so it does not go beyond the structured hints.

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. Nothing is repeated from the title and every word carries meaning.

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 two-parameter read tool with full schema coverage and annotations, the description is barely adequate: it does not define what 'current matchday' means (today, latest played, upcoming) or note the fields projection. No output schema exists, so the description could have clarified the return shape.

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% and both parameters (league_shortcut, fields) are documented in the schema itself. The description mentions only the league context and adds no format or filtering detail beyond the schema, 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 clear verb (Get) and resource (matches for the current matchday of a league), which is specific enough to distinguish a 'current' lookup from the generic sibling openliga_get_matches_by_matchday. It stops short of naming that sibling or explaining how 'current' is derived, so it is clear but not fully differentiated.

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?

The word 'current' implies when to reach for this tool (no season/matchday arguments needed), but there is no explicit when-to-use guidance or reference to the alternative openliga_get_matches_by_matchday. Usage must be inferred from the name and the single required parameter.

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