Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

openligadb_matchday_matches

List all fixtures and results for a single league matchday by league shortcut, season, and group order ID. Find valid matchday or round IDs through group discovery.

Instructions

List one league matchday. Returns all fixtures and results for one discovered league shortcut, season and group order id. Use openligadb_groups to discover valid matchday or round ids.

Input Schema

NameRequiredDescriptionDefault
seasonYesSeason starting year
group_order_idYesMatchday or round id from openligadb-groups
league_shortcutYesExact shortcut from openligadb-leagues

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.6/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 burden. It discloses that this is a read that returns fixtures and results for the discovered scope, which is helpful, but says nothing about ordering, pagination, or what a fixture/result record contains.

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, front-loaded with the core action and followed by the discovery hint. No filler; every clause adds signal.

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 three-required-param read tool with no output schema, the description tells the agent what it retrieves and where to get the id values. Only the shape of returned fixture/result data and any ordering are omitted, which are minor for a list endpoint.

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% and each parameter is already documented (season starting year, group order id from openligadb-groups, exact shortcut from openligadb-leagues). The description restates the discovery requirement for shortcut and group id but adds no syntax or format detail beyond the schema, so 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?

States a specific verb and resource ("List one league matchday") and clarifies the return contents ("all fixtures and results") scoped by league, season and group id. It is clearly distinct from broad tools like openligadb_league_matches, though it never explicitly contrasts with that sibling.

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?

"Use openligadb_groups to discover valid matchday or round ids" gives useful prerequisite routing for the group_order_id. However, there is no guidance on when to choose this over openligadb_league_matches, openligadb_current_matchday, or openligadb_table, so alternative selection is left to inference.

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