Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

openligadb_leagues

List OpenLigaDB league seasons across all sports and optionally filter by season starting year to discover league IDs, shortcuts, and sport types for querying groups or matches.

Instructions

List OpenLigaDB league seasons. Returns every league-season record across all sports. Set season to the season's starting year to use OpenLigaDB's season-specific listing. This is the discovery source for league_shortcut, league_id, and sport; shortcuts may repeat across seasons, and the response is not paginated. The catalog is community-maintained and may include user-created or legacy entries; verify a selected pair through groups or matches.

Input Schema

NameRequiredDescriptionDefault
seasonNoOptional season starting year, e.g. 2026 for 2026/27

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses that the response is unpaginated, that shortcuts may repeat across seasons, and that the catalog is community-maintained with user-created or legacy entries. Those are non-obvious behavioral caveats an agent would otherwise learn only after a bad lookup; only auth/rate-limit context is missing.

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?

Front-loaded with purpose, then scope, then parameter guidance, then caveats — a sensible order with no filler. It is dense in places (four distinct points in four sentences), but every sentence carries information.

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 single optional parameter with no output schema and no annotations, the description covers what is returned (all sports, unpaginated), the parameter's role, and data-quality caveats. Nothing essential to a correct call is missing; only authentication or rate-limit context is absent.

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 coverage is 100% and the schema already documents `season` as an optional starting year with an example, so the description's 'set `season` to the season's starting year' is largely restated. The added value is the warning that shortcuts repeat across seasons, which implies season selection matters, but no format or edge-case detail beyond the schema is provided.

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?

States a specific verb and resource ('List OpenLigaDB league seasons') and immediately scopes it ('every league-season record across all sports'). It also positions the tool in the catalog ('discovery source for league_shortcut, league_id, and sport'), which distinguishes it from the downstream siblings like openligadb_groups and openligadb_matches.

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?

Gives clear when-to-use guidance (first step to obtain league_shortcut/league_id/sport) and a concrete follow-up path ('verify a selected pair through groups or matches'). It does not state an explicit when-not-to-use case, but the discovery-then-verify workflow is unambiguous.

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