Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

openligadb_current_matchday

Fetch current matchday fixtures and results for a specified OpenLigaDB league shortcut, returning active group or matchday matches in clean JSON.

Instructions

Get current matchday fixtures and results. Returns the matches for OpenLigaDB's current group or matchday in one league. This mirrors the source's current-matchday route; a league without a current matchday may return not found. Use openligadb_current_group to see the selected group id or openligadb_matches for a whole season.

Input Schema

NameRequiredDescriptionDefault
league_shortcutYesExact shortcut from openligadb-leagues

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.2/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 and does disclose useful behavior: it mirrors the source's current-matchday route and can return not-found for leagues lacking a current matchday. It implies a read operation but never states read-only/no side effects, and says nothing about result ordering or pagination.

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?

Three short sentences, front-loaded with the return content, then the edge case, then the alternative routes. Every sentence adds distinct information with no redundancy.

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 one-parameter read tool with no annotations and no output schema, the description covers purpose, failure mode, and alternatives well. What remains thin is the shape of a returned 'match' object, which the agent must infer since there is no output schema to lean on.

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 single parameter is documented as 'Exact shortcut from openligadb-leagues', so the schema already does the work. The description only implies the parameter identifies one league and adds no format or example detail beyond the schema.

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 opens with a specific verb and resource ('Get current matchday fixtures and results') and clarifies the scope ('current group or matchday in one league'), which lets an agent distinguish it from season-wide or explicit-matchday siblings. It reads nothing like a restatement of the name.

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 routes the agent explicitly: use openligadb_current_group to discover the group id, or openligadb_matches for a whole season, and it warns that leagues without a current matchday may return not found. It doesn't contrast with openligadb_matchday_matches (explicit matchday) — a natural alternative — and the cited 'openligadb_matches' doesn't exactly match any sibling name (openligadb_league_matches exists).

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