Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fussballde_player

Retrieve a FUSSBALL.DE player profile by ID to view name, team, team type, birth date, and current-season stats for registered players; basic profiles return identity and team details only.

Instructions

Get a FUSSBALL.DE player profile. Returns a player's public profile: name, team, team type, birth date and, for registered players (profile_type full), the current-season statistics such as appearances, minutes played, goals, goals against and cards. Players without a registered profile (profile_type basic) only have name, team and team type. Player ids come from fussballde-player-search, scorer lists, squads and amateur statistics.

Input Schema

NameRequiredDescriptionDefault
player_idYesPlayer id from fussballde-player-search, fussballde-top-scorers, fussballde-team-squad or fussballde-amateur-stats

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations and no output schema, the description carries the full burden and does so well: it documents the returned profile fields and explains the important behavioral difference between full and basic profile types. It also makes clear that this returns public profile data rather than performing a mutation.

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, followed by return-value details and then id-source guidance. Every sentence contributes useful information with no filler.

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?

For a one-parameter read tool with no output schema, the description is complete enough: it explains the resource, the returned fields, the profile-type variation and where ids come from. Nothing essential for correct invocation is missing.

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 the player_id parameter is already fully documented in the schema. The description reinforces where ids come from but does not add format details or validation semantics beyond that.

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 states a specific verb and resource: get a FUSSBALL.DE player profile. It also distinguishes the returned data by profile type, making the tool’s scope clear without needing the schema.

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 implies this is a detail lookup for an already-known player id, and it names the sources from which player ids come: player search, scorer lists, squads and amateur statistics. It stops short of explicitly naming the search sibling as the alternative when no id is available.

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