Crawlora MCP

openligadb_groups

Read-only

List every matchday, round, or phase id for one discovered league shortcut and season. Use a returned groupOrderID with openligadb_matchday_matches or openligadb_last_changed. Some legacy league-season entries may return 404 or an empty list.

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

Input Schema

Name	Required	Description	Default
`season`	Yes	Required season starting year, such as 2026 for 2026/27; discover supported combinations with openligadb_leagues.
`league_shortcut`	Yes	Required exact league shortcut from openligadb_leagues.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's best contribution is the failure-mode disclosure: legacy league-season combinations may return 404 or an empty list. That is real behavioral context an agent needs before retrying or falling back. It does not discuss pagination or list size, but with an output schema present that gap is modest.

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?

Three short sentences, front-loaded with the verb and output, then the downstream consumer, then the caveat. Nothing is redundant and each sentence carries distinct information.

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

Completeness4/5

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

For a two-parameter identifier-list tool with an output schema and safety annotations, the description covers what the agent must know: prerequisites, next step, and error behavior. The only shortfall is not contrasting with the 'current group' siblings, which an agent looking for a live matchday might reasonably confuse this with.

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% and both parameters already document that season is a starting year (e.g. 2026 for 2026/27) and league_shortcut must come from openligadb_leagues. The description reinforces the 'discovered' provenance and single-season scope but adds no syntax or format meaning beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('List') plus the exact resource ('every matchday, round, or phase id') and scopes it to 'one discovered league shortcut and season'. This is clearly separable from siblings like openligadb_matchday_matches or openligadb_current_group, which return matches rather than identifier lists.

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?

Explicitly chains the tool: the returned groupOrderID feeds openligadb_matchday_matches or openligadb_last_changed, and 'one discovered league shortcut' implies openligadb_leagues must run first. It stops short of naming when to prefer this over the sibling openligadb_current_group / openligadb_current_matchday lookups, so the alternatives are only partially addressed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.