Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fussballde_team_squad

Fetch a FUSSBALL.DE team's squad, arrivals, or departures for a season, including appearances, minutes, and goals, to track roster changes and player performance.

Instructions

Get a FUSSBALL.DE team squad. Returns a team's players for a season: the squad (appearances, minutes, goals), arrivals or departures with the columns the site publishes for each. Player names come in the site's Surname, Forename order.

Input Schema

NameRequiredDescriptionDefault
kindNoPlayer list kind, default squad
seasonNoFour-digit season code, default current season
team_idYesTeam id, see fussballde-team

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does meaningful work: it discloses the exact payload shape (squad rows with appearances, minutes, goals; arrivals/departures with site-published columns) and a real gotcha about name formatting ('Surname, Forename'). It leaves out pagination, response size, and any rate-limit or failure 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly packed sentences with zero filler; the resource is front-loaded and the return detail follows. Slightly dense, mixing return-shape and data-format notes into one sentence, but nothing is wasted.

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?

There is no output schema, and the description compensates by describing the returned lists and the fields they contain, plus the name-ordering quirk. Combined with a fully described 3-parameter schema, an agent has everything needed to call and interpret this tool.

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 all three parameters (including the kind enum and season default) are already documented. The description adds only the loose notion of 'a season' and which lists kind selects, duplicating rather than extending the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Get a FUSSBALL.DE team squad') and immediately enumerates the three list kinds it returns. An agent can tell this fetches roster/transfer data rather than match, table, or player-profile data from the many fussballde_* siblings. It stops short of naming a sibling it is not, so a 4 rather than 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: you call it for a team's players in a season. There is no explicit 'use this when you want X instead of fussballde_team / fussballde_player_matches' guidance, nor any precondition such as needing a team_id obtained elsewhere (that hint lives in the schema, not the description).

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