Retrieve the next upcoming match for a league using its exact shortcut, so you can check the league's next fixture without searching through schedules.
Get a league's next match. Returns the next upcoming match for a league shortcut. Use openligadb_leagues to find a shortcut or openligadb_next_team_match for one team.
| 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 burden. "Get"/"Returns the next upcoming match" implies a read-only, single-result operation, but it doesn't say what happens when a league has no upcoming fixtures (empty result vs. error) or whether it requires any authentication. Adequate but not rich behavioral context.
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, zero waste, with the core purpose front-loaded and the routing hints following. Every sentence earns its place.
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 read tool with no output schema and no annotations, the description covers purpose, parameter source, and the nearest alternative. The only real gap is the empty/no-upcoming-match case, which matters for a "next" lookup but is a minor omission otherwise.
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?
Schema coverage is 100% and the schema itself already documents that league_shortcut is the "Exact shortcut from openligadb-leagues." The description reinforces the shortcut source but adds no new format or validation detail beyond the schema. Baseline 3 is appropriate when the schema does the work.
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?
States a specific verb and resource ("Get a league's next match") and immediately distinguishes itself from the sibling openligadb_next_team_match by scoping to a league rather than a team. An agent can select this over the team-level variant without opening either schema.
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?
Explicitly routes the agent: use openligadb_leagues to obtain the required shortcut, and openligadb_next_team_match when the query is about one team. That is clear when-to-use and prerequisite guidance; it lacks only an explicit statement of when this tool is the wrong choice (e.g. historical/last match, which siblings like openligadb_last_match cover).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.