Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

openligadb_next_team_match

Read-only

Get the next match for one OpenLigaDB team id in one league id. Discover league ids with openligadb_leagues and team ids with openligadb_teams.

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_id": "<league_id>",
      "team_id": "<team_id>"
    },
    "name": "openligadb_next_team_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
team_idYesRequired team id from openligadb_teams for this league and season.
league_idYesRequired league id 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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds the key temporal behavior ('next') and ID sourcing, but does not mention what happens when no next match exists or other operational behavior. With an output schema present, return-value details are not required.

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 wasted words, with the primary purpose front-loaded and discovery guidance secondary. It is appropriately sized for a simple two-parameter lookup tool.

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 simple read-only lookup with two required IDs, an output schema, and annotations covering safety, the description is nearly complete. It names the resources needed to obtain valid IDs, though it could do more to distinguish itself from sibling match tools.

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 both parameters are already documented as required IDs from the corresponding discovery tools. The description reinforces the team/league relationship but adds no syntax or constraint meaning beyond the schema.

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?

The description states a clear verb and resource ('Get the next match') scoped to a specific team and league. It does not explicitly distinguish this from close siblings such as openligadb_next_match or openligadb_last_team_match, but the team-and-league scoping makes the purpose understandable.

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?

It helpfully names prerequisite discovery tools for league and team IDs, but it does not say when to use this tool versus similar OpenLigaDB match tools (e.g., next league match, last team match, all team matches). Usage is implied rather than fully guided.

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