Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fussballde_player_matches

Retrieve a FUSSBALL.DE player's match-by-match record for a season and team, including dates, results, goals, substitutions and minutes played.

Instructions

Get a FUSSBALL.DE player's match-by-match record. Returns a registered player's matches for one season and team: date, teams, result and per match the goals, the minute they were substituted in or out, and minutes played. Also lists the player's teams and competitions for the season so another team can be selected with team_id. Basic profiles without registration have no match data.

Input Schema

NameRequiredDescriptionDefault
seasonNoFour-digit season code, default current season
team_idNoTeam id from the teams list of a previous response; default the player's main team
player_idYesPlayer id of a full profile, see fussballde-player

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4/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 discloses meaningful behavior: it enumerates the per-match fields returned, notes one-season/one-team scoping, and warns that unregistered basic profiles have no match data. It does not mention pagination, response size, or error behavior, which keeps it from a 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?

The description is front-loaded with the core action "Get a FUSSBALL.DE player's match-by-match record" and then adds only useful scope, return-field, and eligibility details. Every sentence contributes information with 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?

Given the moderate complexity, full schema descriptions, and no output schema, the description is largely complete: it explains what matches are returned, what fields appear per match, and the no-data case for basic profiles. Minor operational details such as pagination or response limits are omitted.

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 coverage is 100%, so all three parameters are already documented in the schema. The description clarifies the season/team workflow and the purpose of team_id, but it adds little syntactic or semantic detail beyond what the schema descriptions already state.

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 states a specific verb and resource: it gets a FUSSBALL.DE player's match-by-match record and specifies the season/team scope plus return fields. It does not explicitly distinguish itself from closely named siblings like fussballde_player or fussballde_team_matches, so it falls short of a 5.

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 gives clear usage context and an exclusion: the player must be registered/full-profile, because basic profiles have no match data. It also explains that teams and competitions are returned so team_id can be used to switch teams. It does not name alternative tools for finding players or team-level match lists.

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