Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

openligadb_groups

List league matchdays and rounds. Returns every matchday or round id for one discovered league shortcut and season. Pass a returned groupOrderID to openligadb_matchday_matches or openligadb_last_changed.

Instructions

List league matchdays and rounds. Returns every matchday or round id for one discovered league shortcut and season. Pass a returned groupOrderID to openligadb_matchday_matches or openligadb_last_changed. Some legacy league-season entries in the source directory may return 404 or an empty group list.

Input Schema

NameRequiredDescriptionDefault
seasonYesSeason starting year
league_shortcutYesExact shortcut from openligadb-leagues

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries the burden — and it does more than most: it discloses the failure mode (legacy league-season entries may 404 or return an empty group list) and states that the payload is just ids. It stops short of stating read-only semantics explicitly or anything about response shape beyond the id field.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose in four short sentences, each doing work: scope, return contents, next step, and failure mode. Slight redundancy between 'List league matchdays and rounds' and the following sentence, which repeats the matchday/round framing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description still tells the agent the inputs' provenance, the output's key field (`groupOrderID`), where to go next, and how the tool fails on stale league-season pairs. Nothing needed to call it correctly is missing.

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 coverage is 100%, so both parameters are already documented, including 'Season starting year' and 'Exact shortcut from openligadb-leagues'. The description reinforces that the shortcut must be 'discovered' rather than guessed, but adds no format or validation detail beyond the schema — 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?

Specific verb-plus-resource: it lists matchdays/rounds and returns the `groupOrderID` values for one league shortcut and season. That separates it from consumers like `openligadb_matchday_matches`, though it never explicitly contrasts itself with the similarly named `openligadb_current_group` / `openligadb_current_matchday` siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the downstream step clearly: pass the returned `groupOrderID` to `openligadb_matchday_matches` or `openligadb_last_changed`, and 'one discovered league shortcut' implies a prior `openligadb_leagues` lookup. No explicit when-not guidance is given, but the workflow position is unambiguous.

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