Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

openligadb_matches_by_team_id

Read-only

Find recent and upcoming matches across leagues for one exact team id. Both weeks_past and weeks_future are required; zero is allowed. Discover the id 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": {
      "team_id": "<team_id>",
      "weeks_past": "<weeks_past>",
      "weeks_future": "<weeks_future>"
    },
    "name": "openligadb_matches_by_team_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
team_idYesRequired OpenLigaDB team id from openligadb_teams.
weeks_pastYesRequired number of weeks to include before the current date; zero is allowed.
weeks_futureYesRequired number of weeks to include after the current date; zero is allowed.

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

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful scope details about exact team id and required week windows, but does not describe return behavior or ordering beyond what the output schema provides.

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?

Three short sentences are front-loaded with purpose and required-parameter constraints. Every sentence serves a clear role, and nothing is wasted.

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?

The description covers the tool's purpose, prerequisites, and required parameters, which is enough to invoke it correctly. With an output schema present, return values need not be explained, though it could say more about how the time window affects results.

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%, so all three parameters already have documented meanings. The description repeats the required/zero-allowed rules and the team id discovery hint, but adds no semantics 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?

States a specific verb and resource: find recent/upcoming matches across leagues for an exact team id. The scope is clear, but it does not explicitly differentiate itself from close siblings such as openligadb_matches_by_team or openligadb_league_team_matches.

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?

Gives clear usage context: an exact team id is required, both week parameters are required, and zero is allowed. It also points to openligadb_teams for id discovery. It does not name alternative tools or exclusions.

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