Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

openligadb_last_changed

Read-only

Return the exact source update timestamp for one league matchday or round. Check this small timestamp before fetching the full matchday again; if it is unchanged, the fixture list has not been updated.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "league_shortcut": "<league_shortcut>",
      "season": "<season>",
      "group_order_id": "<group_order_id>"
    },
    "name": "openligadb_last_changed"
  }
}

Input Schema

NameRequiredDescriptionDefault
seasonYesRequired season starting year, such as 2026 for 2026/27.
group_order_idYesRequired matchday/round id from openligadb_groups.
league_shortcutYesRequired exact league shortcut from openligadb_leagues.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds non-obvious context beyond them: the call is 'small' (a cheap poll) and defines the meaning of an unchanged result. Return shape is covered by the existing output schema, so nothing critical 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences: the first defines the output, the second delivers the usage rule and the decision semantics. Front-loaded and no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a full output schema, 100% param coverage, and read-only annotations, the description only needs the workflow rationale and the interpretation of an unchanged timestamp — both are present. Nothing an agent needs to call it correctly is missing.

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 the schema already documents league_shortcut, season, and group_order_id fully. The description echoes the domain ('league matchday or round') but adds no syntax or constraint detail beyond the schema; 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?

States a specific verb and resource ('Return the exact source update timestamp') scoped to 'one league matchday or round'. This clearly distinguishes it from the heavier sibling openligadb_matchday_matches that returns the full fixture list.

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?

Gives an explicit workflow rule: check this small timestamp before re-fetching the matchday, and interpret an unchanged value as 'fixture list not updated'. This is a concrete when-to-use plus interpretation policy, not just a vague hint.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources