Retrieve OpenLigaDB's current matchday group for a given league shortcut, so you can identify the active round and fetch its matches.
Get the current league matchday. Returns OpenLigaDB's current group or matchday for a league shortcut. Use openligadb_groups for all matchdays and openligadb_current_matchday for the matches in this group.
| Name | Required | Description | Default |
|---|---|---|---|
| league_shortcut | Yes | Exact shortcut from openligadb-leagues |
Changes observed during successful MCP inspections.
v1.17.18Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It conveys that results reflect the 'current' (live-ish) matchday and is a read-style lookup, but it doesn't say what happens for an invalid/unknown league shortcut or how fresh the data is. Adequate but with visible gaps for a zero-annotation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences with the core action front-loaded and the sibling routing immediately after; nothing is redundant or padded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter, no-output-schema lookup tool this is nearly complete: purpose and sibling disambiguation are covered. The remaining gap is that it never clarifies what a 'group' payload actually contains versus a plain matchday.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There is a single parameter with 100% schema description coverage ('Exact shortcut from openligadb-leagues'), so the schema already does the documenting. The description mentions 'league shortcut' but adds no format, casing, or validation detail beyond what the schema states.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource (get the current group/matchday for a league shortcut) and explicitly distinguishes itself from two named siblings. The only slight weakness is the group-vs-matchday terminology, which it mentions but doesn't fully disambiguate.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It routes the agent clearly: use `openligadb_groups` for all matchdays and `openligadb_current_matchday` for the matches within this group, which implies this tool is for just the single current one. There's no explicit 'when not to use' or prerequisite note, but the alternative-selection guidance is concrete.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.