Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fussballde_team

Retrieve a FUSSBALL.DE team profile by team ID, including standings, competitions, venues, club details, and season-by-season history.

Instructions

Get a FUSSBALL.DE team. Returns one team page: name, team type, federation, standing summary (competition, table position, points, goal ratio), current competitions, home venues, the club profile (founding year, address, contact) and the team's season-by-season history with final placings and the highest league reached. Use fussballde-team-matches and fussballde-team-squad for fixtures and players.

Input Schema

NameRequiredDescriptionDefault
team_idYesTeam id from fussballde-matchday, fussballde-table or fussballde-club

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. 'Get' and 'Returns' imply a read-only detail retrieval, and the long list of returned fields discloses what the agent will receive, but it does not explicitly state side-effect safety, auth requirements, rate limits, or error behavior.

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, then efficiently lists the returned data before closing with sibling routing. Despite the enumeration, every part earns its place because there is no output schema to document return values.

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?

The tool has one required parameter, no annotations, and no output schema; the description compensates by enumerating the returned team page contents and naming alternative tools for fixtures and squad data. It does not mention how to discover `team_id`, but the schema covers that source directly, leaving only minor implicit behavior undocumented.

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% and the `team_id` parameter already documents its source: matchday, table, or club tools. The main description does not add further meaning beyond the schema, so the baseline of 3 is appropriate.

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 opens with a specific verb and resource: 'Get a FUSSBALL.DE team,' then enumerates the returned data including standing summary, competitions, venues, club profile, and season history. It also explicitly distinguishes this tool from `fussballde-team-matches` and `fussballde-team-squad` for fixtures and players, so an agent can identify the tool without opening 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?

The description gives clear sibling routing: use `fussballde-team-matches` and `fussballde-team-squad` for fixtures and players. It does not explicitly say when to prefer this tool over related club-level tools, and the hyphenated sibling names differ slightly from the actual underscore-based tool names, but the intended usage is clear.

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