Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fussballde_amateur_stats

Retrieve FUSSBALL.DE amateur football rankings, including top teams, goal ratios, highest-scoring matches, and top scorers, filtered by season, team type, and federation.

Instructions

Get FUSSBALL.DE amateur top statistics. Returns a page of one of the ten Top-Amateurstatistiken rankings (Kreisklasse to Regionalliga, championship matches): top teams by goals, goal ratio, goals against and points average, highest-scoring matches, biggest draws, and top scorers by goals, ratio and goals in one match per week or season. Filter by season, team type and federation and page with limit and offset. A ranking is bounded to roughly its top 200 entries; final marks the last page.

Input Schema

NameRequiredDescriptionDefault
statYesRanking id
limitNoRows per call, 1 to 100, default 30
offsetNoNumber of rows to skip, 0 to 1000, default 0
seasonNoFour-digit season code, 2627 for 2026/27; the site offers the current and previous season
team_typeNoTeam type id; omit for all
federation_idNoFederation id; omit for all federations

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 supplied, the description carries the burden and does much of it: it discloses that results are paged, that a ranking is capped at roughly 200 entries, and that a `final` flag marks the last page — none of which is derivable from the input schema. It does not mention rate limits or whether a federation/team-type filter narrows the entry count.

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?

Three sentences, front-loaded with the purpose and the ranking catalogue before the filtering and paging mechanics. The ranking enumeration is dense but earns its place; nothing is redundant.

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?

No output schema exists, so the description must explain the return shape, and it does: a page of a bounded ranking with a `final` end-of-results marker plus the full catalogue of what each ranking contains. Combined with the fully documented six-parameter schema, an agent has enough to call this correctly.

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 baseline is 3. The description restates the filter dimensions but adds no meaning the schema lacks — notably it never maps the opaque enum ids "1"-"10" onto the ten rankings it spends a sentence enumerating, which is the highest-value detail it could have added for the required `stat` parameter.

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 FUSSBALL.DE amateur top statistics") and then enumerates the ten ranking families covered, from team goals to top scorers. An agent can tell this returns curated amateur leaderboards rather than a table or match list. It never distinguishes itself from nearby siblings such as fussballde_top_scorers or fussballde_national_top_scorers, which is the one gap.

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 implied rather than stated: the description lists the available filters (season, team type, federation) and the paging parameters, which tells an agent how to narrow a query. There is no explicit "use this when..." statement, no exclusions, and no pointer to an alternative tool for a different ranking need.

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