Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fussballde_federation

Retrieve a FUSSBALL.DE federation or regional association profile by ID or region, including contact details, leadership, club and team counts, and recent news.

Instructions

Get a FUSSBALL.DE federation or regional association. Returns the profile of one of the 22 federations (the DFB and the regional and state associations) or of one of the five regional associations (Norddeutscher, Nordostdeutscher, Süddeutscher, Südwest and Westdeutscher): name, address, website, president, club, member and team counts, and the latest news items. Provide exactly one of federation_id and regional_association.

Input Schema

NameRequiredDescriptionDefault
federation_idNoFederation id; provide exactly one of federation_id and regional_association
regional_associationNoRegional association; provide exactly one of federation_id and regional_association

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the returned profile fields and mentions latest news items, and the verb 'Get' implies a read-only operation. It does not, however, add details about authentication, rate limits, error cases, or side effects.

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 three well-structured sentences, front-loaded with the tool's purpose, followed by returned data and a precise parameter constraint. Every sentence contributes useful information with no wasted text.

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?

For a simple two-parameter read tool with no output schema, the description is nearly complete: it explains what is retrieved, lists the profile fields, and states the one-of parameter rule. Minor gaps around pagination, auth needs, or invalid-input behavior are acceptable given the tool's simplicity.

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 schema already documents both parameters and the 'provide exactly one' constraint. The description adds some context by naming the five regional associations and stating that there are 22 federations, but it does not map the federation ID enum values or add substantial new parameter semantics.

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?

The description gives a specific verb and resource ('Get a FUSSBALL.DE federation or regional association') and enumerates the returned profile fields. It is clear what the tool does, though it does not explicitly contrast itself with sibling tools such as fussballde_club or fussballde_team.

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?

The description implies when to use the tool by stating its purpose, and it specifies that exactly one of the two lookup modes must be provided. However, it does not explicitly say when to use this tool versus alternatives or explain any exclusions.

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