Retrieve a league's last played match using its shortcut and return the result for that league.
Get a league's last match. Returns the most recently played match for a league shortcut. Use openligadb_leagues to find a shortcut or openligadb_last_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 full burden; it does make clear this is a plain retrieval ('Returns the most recently played match'), implying no mutation. It does not mention what happens when a league has no played matches yet (off-season or season start), nor any auth or rate-limit behavior, which would matter for a single-record lookup that can return empty.
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?
Two short sentences, front-loaded with the action and return value, then the disambiguation and prerequisite. Every clause earns its place with no repetition of the tool name.
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, the description covers purpose, parameter provenance, and the key alternative. The only meaningful gap is the empty-result / no-match-played case, which is the main behavioral uncertainty left for an agent.
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 field already says 'Exact shortcut from openligadb-leagues', so the description adds little beyond restating that the input is a league shortcut. The pointer to openligadb_leagues is useful context but does not add syntactic or format meaning beyond the schema.
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 last match') and immediately clarifies scope as 'the most recently played match for a league shortcut', which distinguishes it from time-window or team-scoped siblings. An agent can tell it apart from openligadb_last_team_match and openligadb_next_match without reading any 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 to openligadb_leagues for obtaining a shortcut and to openligadb_last_team_match when a single team is the subject, so the main selection question is answered. It stops short of covering other close alternatives such as openligadb_next_match (future fixture) or openligadb_league_matches, leaving some ambiguity about league-wide fixtures vs. this single last result.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.