Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

openligadb_table

Fetch a league season's standings table by exact league shortcut and season starting year to get structured JSON for analysis.

Instructions

Get a league season's table. Returns the league standings for one discovered shortcut and season. OpenLigaDB's documented getgrouptable path currently returns HTTP 404 on tested league/season pairs; this endpoint uses the live getbltable resource.

Input Schema

NameRequiredDescriptionDefault
seasonYesSeason starting year
league_shortcutYesExact shortcut from openligadb-leagues

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.7/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 full burden. It usefully discloses an upstream quirk (getgrouptable 404s, this uses getbltable) which the agent could not otherwise know, but it says nothing about auth needs, rate limits, or freshness of the standings data.

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, each earning its place: the first front-loads what the tool returns, the second explains the API quirk. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with no output schema, the definition covers inputs and the upstream quirk but never says what a standings row contains (rank, team, points, goal difference?) or whether partial/empty tables are returned for unplayed seasons. That leaves a real gap for an agent that must interpret the result.

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 both parameters are already documented, including the 'Exact shortcut from openligadb-leagues' hint. The description restates that requirement ('one discovered shortcut and season') but adds no format detail, valid season ranges, or edge-case behavior beyond the schema; baseline 3 applies.

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 states a specific verb and resource: 'Get a league season's table' / 'Returns the league standings for one discovered shortcut and season'. It is clearly narrower than siblings like openligadb_matches or openligadb_league_matches, but it does not explicitly distinguish itself from openligadb_groups or openligadb_current_group, which an agent could plausibly confuse with a standings tool.

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?

It signals a prerequisite workflow by requiring a 'discovered' shortcut, implying openligadb_leagues runs first, and it explicitly steers the agent toward this endpoint over the documented `getgrouptable` path that returns 404. What is missing is any explicit negative guidance — e.g. when a group table rather than a full league table is wanted.

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