Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

openligadb_league_matches

Retrieve all fixtures and results for one league shortcut and season, giving the complete match list needed to review schedules and outcomes.

Instructions

List a league season's matches. Returns every fixture and result recorded for one league shortcut and season. Use openligadb_groups and openligadb_matchday_matches for one round, or openligadb_leagues to discover valid league-season pairs. The source returns the full list without pagination.

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

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

With no annotations present, the description carries the full burden and usefully discloses that the source returns the full list without pagination. It also implies read-only behavior through "List" and "Returns," but it does not discuss authentication, rate limits, or error behavior, leaving some gaps for a no-annotation tool.

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?

The description is four tight sentences with the primary purpose front-loaded, followed by return scope, alternatives, and pagination behavior. Every sentence contributes useful information and there is no filler.

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 simple two-parameter read tool with no output schema and no annotations, the description covers the core behavior, alternative routing, and pagination absence. It could be slightly richer about response fields or source limitations, but it is sufficient for correct invocation.

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%, so both parameters are already documented in the schema. The description reiterates that one league shortcut and season are required and points to `openligadb_leagues`, but it adds little semantic detail beyond the schema, making the baseline 3 appropriate.

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?

The description opens with a specific verb and resource: "List a league season's matches," then clarifies that it returns "every fixture and result recorded for one league shortcut and season." This clearly distinguishes the tool from sibling tools that handle individual rounds or league discovery.

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?

It explicitly names alternatives for different needs: `openligadb_groups` and `openligadb_matchday_matches` for one round, and `openligadb_leagues` for discovering valid league-season pairs. This gives the agent clear routing guidance without needing to inspect sibling schemas.

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