Skip to main content
Glama

Openligadb

by io.github.pipeworx-io

Get Matches

get_matches
Read-onlyIdempotent

Get football / soccer match results / scores and fixtures for a league and season (e.g. Bundesliga). Optionally narrow to a single matchday. Returns teams, kickoff datetime, final score, and whether each match is finished.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
leagueYesLeague shortcut, e.g. 'bl1' (Bundesliga), 'bl2' (2. Bundesliga), 'bl3' (3. Liga), 'dfb' (DFB-Pokal).
seasonYesSeason start year, e.g. "2024".
matchdayNoOptional matchday number (1-based).

TDQS

A4/5.0
Behavior4/5

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

Annotations already confirm read-only, idempotent, non-destructive. The description adds context about returned fields (teams, kickoff, score, finished status), which is helpful beyond the annotations.

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-sentence description efficiently states the core function, optional narrowing, and return data. No extraneous words; every sentence adds 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?

Although there is no output schema, the description lists the key return fields. For a simple read-only tool, this is sufficient to set expectations.

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?

Input schema covers 100% of parameters with clear descriptions and examples. The description does not add significant new meaning beyond what the schema provides, so baseline 3 is appropriate.

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?

The description clearly states the tool retrieves football/soccer match results, scores, and fixtures for a league and season. It specifies return fields (teams, datetime, score, status) and distinguishes from siblings like list_leagues or get_table.

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 mentions optional scope (single matchday) but does not provide explicit guidance on when to use this tool over alternatives like current_matchday or bet_research.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Openligadb toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, with detailed descriptions differentiating similar tools like ask_pipeworx, ask_pipeworx_grounded, and deep_research. However, some overlap exists between ask_pipeworx and ask_pipeworx_beta, as both serve as universal routers with only minor routing improvements.

Naming Consistency2/5

Tool names follow inconsistent patterns: some use snake_case (ask_pipeworx, entity_profile), others use lowercase single words (forget, recall), and some use camelCase (bet_research, deep_research). This mix of conventions makes the naming scheme unpredictable.

Tool Count3/5

With 35 tools, the server covers a wide range of data sources, but the count feels slightly heavy for the apparent scope. Several tools serve meta-purposes (discover_tools, suggest_questions) or specialized functions (polymarket_arbitrage), adding to the complexity.

Completeness4/5

The tool set offers comprehensive coverage for financial, economic, drug, and news data, including comparison and grounding capabilities. However, the football-related tools are limited to German leagues, leaving a minor gap for other sports or regions.

Resources