Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fussballde_matchday

Fetch FUSSBALL.DE competition matches for the current, numbered, or date-based matchday, including teams, kick-off, score, status, and cup rounds.

Instructions

Get FUSSBALL.DE matches of a competition matchday. Returns the matches of a competition's current matchday, of a numbered matchday (matchday, 1 to the competition's matchday count, reported as matchday_count) or of the matchday around a date. Each match has teams, date, kick-off time, score and status (finished, scheduled, cancelled and the other values listed below). Cups and tournaments have no numbered matchdays; for them the response lists the competition's rounds (each round id works as competition_id to read that round) and labels every match with its round. Dates, times and scores are decoded from the site's obfuscated glyph fonts.

Input Schema

NameRequiredDescriptionDefault
dateNoMatchday date as YYYY-MM-DD; omit for the current matchday; cannot be combined with matchday
matchdayNoMatchday number, 1 to the competition's matchday count (34 for the Bundesliga); cannot be combined with date
competition_idYesCompetition id from fussballde-competitions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well. It discloses the return contents (teams, date, kick-off time, score, status with example enum values), explains how cups and tournaments behave (rounds instead of numbered matchdays), and notes that dates, times, and scores are decoded from obfuscated glyph fonts. This is substantive behavioral context beyond the schema.

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?

The description is front-loaded with the core action and then layers in mode selection, return details, and edge cases efficiently. It is dense but every sentence adds useful information. A slightly tighter structure could improve scannability, but it is not bloated.

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?

Given the absence of an output schema, the description fully compensates by describing the returned match fields, status values, and the special cup/tournament rounds behavior. For a three-parameter read tool, it provides everything an agent needs to invoke it correctly and understand what comes back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful context beyond the schema: it explains that omitting date yields the current matchday, that matchday ranges from 1 to the competition's matchday count, and that cup/tournament round ids also work as competition_id. These additions improve parameter understanding, though they largely reinforce rather than extend the schema.

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?

The description clearly states a specific verb and resource: 'Get FUSSBALL.DE matches of a competition matchday.' It scopes the operation to competition matchdays and explains the three retrieval modes, which helps distinguish it from team- or club-centric match tools. However, it does not explicitly name or contrast with sibling tools like fussballde_match_calendar or fussballde_team_matches, so it stops short of complete sibling differentiation.

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 clearly explains the three ways to use the tool: current matchday, a numbered matchday, or a matchday around a date. The schema also documents the mutual exclusivity between date and matchday. What it lacks is explicit guidance on when to choose this tool over adjacent siblings such as fussballde_match_calendar or fussballde_team_matches.

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