Crawlora MCP

openligadb_matches_by_team

Read-only

Find recent and upcoming matches across leagues by partial team name and week windows. Both weeks_past and weeks_future are required; zero is allowed. Use openligadb_matches_by_team_id when you have an exact team id.

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": {
      "team_filter": "<team_filter>",
      "weeks_past": "<weeks_past>",
      "weeks_future": "<weeks_future>"
    },
    "name": "openligadb_matches_by_team"
  }
}

Input Schema

Name	Required	Description
`weeks_past`	Yes	Required number of weeks to include before the current date; zero is allowed.
`team_filter`	Yes	Required partial team-name text, such as Bayern München.
`weeks_future`	Yes	Required number of weeks to include after the current date; zero is allowed.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.5/5.0

Behavior4/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 useful behavioral detail beyond that: cross-league scope, the partial-match semantics, and the mandatory-but-zero-allowed nature of both week parameters. It does not discuss result ordering or limits, but the output schema exists to describe returns.

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 with no filler. The core purpose and the key constraint (both weeks required) are front-loaded, and the sibling disambiguation comes last as a routing note.

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?

Combined with a 100%-documented schema, explicit annotations, and an output schema covering return values, the description gives an agent everything needed to select and invoke the tool correctly. Nothing material 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%, and the schema already documents all three parameters including the 'zero is allowed' note. The description reinforces requiredness and partial-name matching but adds little semantic meaning the schema does not already carry, so 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 ('Find') plus resource ('matches'), scope (recent and upcoming, across leagues) and matching mechanism (partial team name with week windows). It also explicitly names the sibling it is not, so an agent can differentiate it from openligadb_matches_by_team_id immediately.

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?

Provides an explicit routing rule: use this tool for partial team names, and use openligadb_matches_by_team_id when an exact team id is available. It also clarifies that both week parameters are required and that zero is a valid value, removing the most likely invocation error.

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

All Crawlora MCP tools Inspect

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

Need Help?