Crawlora MCP

openligadb_league_matches

Read-only

Return every fixture and result recorded for one league shortcut and season. Use openligadb_groups and openligadb_matchday_matches for one round, or openligadb_league_team_matches for a team-name fragment.

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_league_matches"
  }
}

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.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds meaningful behavioral context by saying the tool returns *every* fixture and result for the season, warning the agent to expect a season-wide result set, but it does not address volume, pagination, or truncation for long seasons.

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?

Two sentences, zero filler. The primary scope statement is front-loaded and the sibling routing follows immediately after.

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?

With an output schema present, return format needn't be explained, annotations cover the read-only/open-world profile, and both params are fully documented. The only residual gap is that a whole-season fetch is potentially large and the description says nothing about result size or pagination.

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 description coverage is 100% and both parameters are documented in the schema, including the season-as-starting-year convention and discovery via openligadb_leagues. The description only restates the two inputs at a high level, adding no syntax or lookup detail 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 and resource: 'Return every fixture and result recorded for one league shortcut and season.' The scope (one league + one season, whole season rather than a round) is explicit, so the agent can distinguish it from round-scoped and team-scoped siblings without opening a schema.

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

Usage Guidelines5/5

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

Names two alternatives with their selecting conditions: openligadb_groups and openligadb_matchday_matches 'for one round', and openligadb_league_team_matches 'for a team-name fragment'. This is explicit when-to-use / when-to-use-something-else guidance rather than implied context.

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.

Resources

Need Help?