Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

openligadb_last_match

Read-only

Return the most recently played match record for one league shortcut, including teams, kickoff, status and results. Discover shortcuts with openligadb_leagues; use openligadb_last_team_match for one team within a league.

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>"
    },
    "name": "openligadb_last_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
league_shortcutYesRequired exact league shortcut from openligadb_leagues, including its original case and characters.

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.2/5.0
Behavior3/5

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

readOnlyHint=true and openWorldHint=true already declare the safety and external-data profile, so the description only needs to add beyond that. It confirms the temporal semantics ('most recently played'), but the field list duplicates the output schema and it says nothing about edge cases such as a league with no completed matches or which season 'last' resolves against.

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, zero filler: the primary behavior comes first, followed by the two routing pointers. Every clause earns its place.

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 a full output schema and readOnly/openWorld annotations, the description covers purpose, routing and payload expectations adequately. Minor gap: no statement about behavior when no match exists or how far back 'most recent' reaches.

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 already documents that the exact league shortcut (case and characters preserved) must come from openligadb_leagues. The description reinforces the discovery path but adds no syntax or format detail beyond the schema, so the baseline of 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 most recently played match record for one league shortcut") and even enumerates the payload fields. It distinguishes itself from openligadb_last_team_match by scope (league vs. team) and from openligadb_next_match implicitly by 'most recently played'.

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?

Explicitly routes shortcut discovery to openligadb_leagues and team-scoped lookups to openligadb_last_team_match, so an agent knows when to pick a sibling instead. Usage is stated, not implied.

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