Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

openligadb_last_changed

Retrieve a league season matchday's source update timestamp to decide whether refetching the full matchday is necessary.

Instructions

Get a matchday's last update time. Returns OpenLigaDB's source update timestamp for one league, season and matchday. Use this cheap check before refetching the full matchday when the timestamp is unchanged.

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

A4.2/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 disclosure burden. It helpfully characterizes itself as a 'cheap check' and states the return is a source update timestamp, but it says nothing about the timestamp format, error behavior when a matchday does not exist, or any rate/access constraints.

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 tight sentences, with the core purpose and the key optimization guidance front-loaded. Every sentence carries distinct information (what it returns, what scope, when to call it) 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?

With no output schema and no annotations, the description does the important work: it names the return value and the intended workflow. It falls slightly short on timestamp format and failure/missing-matchday behavior, but for a simple read-only lookup it is largely complete.

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 all three parameters are already documented (season, group_order_id from openligadb-groups, league_shortcut from openligadb-leagues). The description restates the trio as 'league, season and matchday' but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 states a specific verb and resource ('Get a matchday's last update time') and clarifies the return ('OpenLigaDB's source update timestamp for one league, season and matchday'). It implicitly distinguishes itself from the heavier matchday-matches fetch by framing itself as a pre-check, so an agent can tell what it does and what it is not.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit when-to-use rule: 'Use this cheap check before refetching the full matchday when the timestamp is unchanged.' That names both the condition (timestamp unchanged) and the alternative course of action (full matchday refetch), leaving little 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