Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fussballde_competition_options

Lists FUSSBALL.DE team types, leagues, and areas for a federation, season, and competition type, providing federation-specific IDs to pass to the competitions tool.

Instructions

List FUSSBALL.DE team types, leagues and areas. Returns the team types (Herren, Frauen, A-Junioren, ...), the leagues (Spielklassen) of each team type and the areas (Gebiete) of each league for one federation, season and competition type. Team type, league and area ids are federation-specific, so take them from this response and pass them to fussballde-competitions.

Input Schema

NameRequiredDescriptionDefault
seasonYesFour-digit season code, 2627 for 2026/27
federation_idYesFederation id
competition_typeNoCompetition type id, default 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.2/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden. It discloses the three-level nested shape of the response, the scoping to one federation/season/competition type, and the critical property that ids are federation-specific rather than global. It does not mention result size, rate limits, or whether the federation list itself is enumerable, which are the remaining gaps.

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?

Two sentences, both earning their place: the first states what the tool lists, the second states what it returns and the id-locality rule plus the downstream tool. Front-loaded and free of 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?

With no annotations and no output schema, the description must stand in for both, and it does so by describing the return hierarchy and the id-locality constraint. Adequate to call correctly. Slightly short of 5 because nothing is said about response size or whether a default competition_type applies when 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 description coverage is 100%, and the schema already documents the season code format, the federation enum, and the competition type default. The description only restates the scoping dimensions in prose ('one federation, season and competition type'), adding no syntax or edge-case guidance. That is baseline behavior when the schema does the heavy lifting.

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?

A precise verb-plus-resource statement ('List FUSSBALL.DE team types, leagues and areas') followed by an explicit enumeration of what the response contains (team types, Spielklassen per team type, Gebiete per league). An agent knows exactly what this returns and how it differs from fussballde_competitions, which is named directly.

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 tells the agent this is a lookup step whose output feeds `fussballde-competitions`, and warns that team type/league/area ids are federation-specific so they must come from this response. That is strong routing. It never states the inverse (when not to call this, e.g. if the caller already has ids), so it falls short of a full 5.

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