Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

openligadb_league_team_matches

Read-only

Find matches in one league season by a partial team name. Use openligadb_teams for exact names and ids; numeric-only fragments are rejected because the upstream route treats numeric path segments as matchday ids.

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

Input Schema

NameRequiredDescriptionDefault
seasonYesRequired season starting year, such as 2026 for 2026/27.
team_filterYesRequired partial team-name text. The upstream matches this fragment within the selected league season; use openligadb_teams to find exact team names.
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.2/5.0
Behavior4/5

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

Annotations only cover read-only and open-world; the description contributes genuinely non-obvious behavior — that numeric-only fragments are rejected because the upstream route parses numeric path segments as matchday ids. That is the kind of hidden failure mode an agent cannot get from the schema. It says nothing about result ordering, pagination, or empty-result behavior.

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 core capability comes first and the routing/validation caveat follows, which is the right order for an agent scanning before a call.

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?

Three required params are fully described in the schema, an output schema exists, and annotations carry the safety profile. The description only needs to add scope, routing, and the numeric-fragment trap — all of which it does.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns a bump by adding a constraint the schema omits — the substring must not be purely numeric, and exact names/ids should come from openligadb_teams. The league_shortcut and season parameters are left entirely to 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?

States a specific verb+resource+scope: find matches constrained to one league season via a partial team name. That scope does implicitly separate it from openligadb_league_matches (whole league) and openligadb_matches_by_team (no season/league bound), but those siblings are never named, so the differentiation is inferential rather than explicit.

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

Usage Guidelines4/5

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

Routes the agent to openligadb_teams whenever exact names or ids are needed, and adds a hard precondition (no numeric-only fragments). It gives no guidance against the very similar openligadb_matches_by_team / openligadb_matches_by_team_id siblings, which is the main alternative an agent would weigh.

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