Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fussballde_club_matches

Retrieve FUSSBALL.DE fixtures and results for a club across senior and youth teams, filtered by match kind, date window, and competition, with paging for complete schedules.

Instructions

Get FUSSBALL.DE fixtures and results of a club. Returns the fixtures and results across all of a club's teams (senior and youth). all (default) is the club match plan for a date window (default the current season) optionally for one competition kind and paged with limit and offset; next is the next fixtures and previous the latest results. Each match names its competition and team type.

Input Schema

NameRequiredDescriptionDefault
kindNoMatch list kind, default all
limitNoMatches (kind all only) per call, 1 to 50, default 10
offsetNoNumber of matches to skip, 0 to 1000, default 0
club_idYesClub id from fussballde-club or fussballde-club-search
date_toNokind all only: last day as YYYY-MM-DD, default 30 June of the season
date_fromNokind all only: first day as YYYY-MM-DD, default 1 July of the current season
competition_kindNokind all only: competition kind id; omit for all kinds

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses default behaviors (current season window: 1 July to 30 June), that results span all teams including youth, and what each match record names (competition and team type). It omits any statement about failure modes, rate limits, or whether pre-season dates shift, so it is solid but not exhaustive.

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 dense sentences, front-loaded with what the tool returns and immediately followed by the mode semantics. No filler and no repetition of schema text verbatim.

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 7-parameter, no-output-schema tool, the description covers mode selection, defaults, pagination and the shape of returned match records, which is enough to call it correctly. It leaves unstated what a match record contains beyond competition and team type (score, date, teams), a minor gap given there is no output schema.

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 baseline is 3; the description earns extra credit by adding cross-parameter semantics the schema only implies per-field: that `limit`, `offset`, `date_from`, `date_to` and `competition_kind` are valid only for `kind=all`, and that the date window defaults to the current season. It doesn't add value on `club_id` beyond what the schema already states.

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 (fixtures and results of a club) and pins down the scope: all of a club's teams, senior and youth. The three-way `kind` split (all/next/previous) is spelled out, so an agent knows the tool is a club-level aggregated match plan rather than a single-team feed.

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?

Explains when each `kind` applies: `all` for a date window with optional competition filter and paging, `next` for upcoming fixtures, `previous` for latest results, and notes that `limit`/dates/`competition_kind` only apply to `all`. It does not name the obvious siblings (fussballde_team_matches, fussballde_match_plan) to steer the agent away from them, which keeps it short of a 5.

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