Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fussballde_club

Retrieve a FUSSBALL.DE club by ID for federation, profile facts, team counts, and season-specific teams with competitions; use season and competition kind filters to narrow results.

Instructions

Get a FUSSBALL.DE club. Returns one club: name, federation, team counts, profile facts (founding year, address, website) and the club's teams with their competitions and team type. Teams are those of the current season; set season for an earlier one and competition_kind to keep only teams in championships, cups, friendlies and so on. Club ids appear as club_id on teams and matches.

Input Schema

NameRequiredDescriptionDefault
seasonNoFour-digit season code such as 2526; default current season
club_idYesClub id from a team or match, e.g. 00ES8GN8N400008VVV0AG08LVUPGND5I
competition_kindNoCompetition kind id; omit for all kinds

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?

With no annotations, the description does real work: it discloses that exactly one club is returned, that teams default to the current season and can be narrowed by competition_kind, and what fields are included. It omits failure behavior for an invalid club_id and says nothing about response size or pagination, but the read-only 'Get' framing and data-scope disclosure are substantial.

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?

Purpose is front-loaded, then return shape, then scoping options — a sensible order with no filler. The single long enumerative sentence is dense but every clause carries information; slight listiness keeps it from a 5.

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?

There is no output schema, and the description compensates by listing the returned fields and by clarifying the season/filter defaults for the embedded teams. All three parameters are addressed; only error handling and identity/permission expectations are missing, which is minor for a read-only lookup.

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 the baseline is 3; the description exceeds it by explaining that `season` selects an earlier season and that `competition_kind` restricts teams to championships, cups, friendlies, etc. — semantics the enum of numeric ids cannot convey on its own.

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?

"Get a FUSSBALL.DE club" gives a specific verb and resource, and the following sentence enumerates exactly what data comes back (name, federation, team counts, profile facts, teams with competitions). It never names a sibling such as fussballde_club_search or fussballde_team, so the agent must infer the distinction from the club_id mention alone.

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: the description notes that club ids appear as `club_id` on teams and matches, which hints at when the tool is applicable. It never states the exclusion or the alternative path (e.g., use fussballde_club_search when you only have a club name), so an agent has no explicit routing rule.

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