Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fussballde_match_plan

Retrieve a competition's full FUSSBALL.DE season schedule with fixtures and results, optionally filtered by team or date window; cup rounds are included.

Instructions

Get the full FUSSBALL.DE match plan of a competition. Returns every match of a competition's season (fixtures and results), including the earliest matchdays, optionally filtered to one team and a date window; the date window is applied by the site, so a narrow window is cheaper than filtering a full season. Cups and tournaments are assembled round by round: every match carries its round and the response lists the rounds with their ids. Use it for a complete schedule; use fussballde-matchday for one matchday.

Input Schema

NameRequiredDescriptionDefault
date_toNoLatest match date as YYYY-MM-DD; default is the whole season
team_idNoTeam id to keep only that team's matches
date_fromNoEarliest match date as YYYY-MM-DD; default is the whole season
competition_idYesCompetition id from fussballde-competitions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.7/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 well: it discloses return content (fixtures and results, earliest matchdays), structure for cups (round/rounds with ids), and a real performance trait (the site applies the date window, so a narrow window is cheaper). It stops short of stating auth or rate-limit behavior, so not a full 5.

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?

Front-loads the purpose in the first sentence, then layers useful detail (return scope, performance note, cup round structure, sibling routing). Every sentence earns its place with no redundancy.

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?

No output schema and no annotations, yet the description explains what comes back (matches, rounds with ids), how filters behave, and cost characteristics — everything an agent needs to invoke it correctly. Return-value structure is covered without an 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, but the description adds genuine value beyond the schema: it explains that the date window is applied server-side and that narrowing it is cheaper than filtering a full season, plus clarifies team filtering scope. That's semantics the raw schema 'earliest/latest date' fields don't convey on their own.

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 'Get' plus resource 'full FUSSBALL.DE match plan of a competition' and scope (fixtures, results, season, earliest matchdays). It's clearly distinguished from the sibling fussballde_matchday by contrast, so an agent can pick it 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?

Explicitly says 'Use it for a complete schedule; use `fussballde-matchday` for one matchday' — a named alternative with the condition that selects it. It also notes the optional team/date filters, so both the use case and the routing are stated.

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