Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fussballde_table

Retrieve FUSSBALL.DE competition standings as overall, home/away, round, fair-play, or cross tables, optionally as they stood after a chosen matchday.

Instructions

Get a FUSSBALL.DE competition standings table. Returns a competition's standings in one view: overall, home_away (home and away tables), rounds (first and second half-season tables), fairness (fair-play table) or cross (cross table of results between every pair of teams). Set matchday to get the standings as they were after that matchday (not available for fairness). Rows carry position, team, played, won, drawn, lost, goals and points where the view has them, plus the raw cells.

Input Schema

NameRequiredDescriptionDefault
viewNoStandings view, default overall
matchdayNoReturn the standings after this matchday, 1 to the competition's matchday count; not available for the fairness view
competition_idYesCompetition id from fussballde-competitions

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 carries the full burden and does so well: it clarifies that this is a read of a single competition's table, defines each view's meaning, discloses that matchday produces a historical snapshot (not available for fairness), and describes row contents plus raw cells. It omits auth/permission notes and pagination, which are minor for a read-only standings endpoint.

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 in the first sentence, followed by view definitions and matchday behavior, then row contents. It is information-dense with little waste; the only minor cost is a fairly long enumeration, but each clause adds distinct value.

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?

No output schema exists, yet the description describes the returned rows (position, team, played, won, drawn, lost, goals, points, raw cells), covering the return surface. Combined with full param semantics and the matchday/fairness constraint, an agent has enough to call it correctly; only edge cases like error behavior are absent.

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 baseline is 3, but the description adds real meaning beyond the schema by defining what each enum view represents (home/away tables, first/second half-season, fair-play, cross-pair results) and reiterating the matchday restriction semantically. This meaningfully helps the agent choose a view value.

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 (Get) and resource (FUSSBALL.DE competition standings table), and enumerates the distinct views (overall, home_away, rounds, fairness, cross) so the agent knows exactly what output shape to expect. It doesn't explicitly differentiate from siblings like fussballde_competitions or fussballde_top_scorers, which keeps it from a 5.

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 explains how to configure the tool (which view to pick, when to use matchday for point-in-time standings, and that matchday is unavailable for fairness), which is configuration guidance. It does not state when to choose this tool over alternatives or prerequisites for obtaining competition_id beyond the schema hint, so usage is implied rather than explicit.

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