Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

openligadb_matches_by_team

Find recent and upcoming matches across leagues by entering a partial team name and past/future week ranges; use zero for either range to narrow results around today.

Instructions

Find recent and upcoming matches by team name. Returns matches around the current date across leagues for a partial team-name fragment. Both week counts are required; zero is allowed. Use openligadb_matches_by_team_id when you have a team id.

Input Schema

NameRequiredDescriptionDefault
weeks_pastYesNumber of weeks before today to include; zero is allowed
team_filterYesPartial team-name fragment
weeks_futureYesNumber of weeks after today to include; zero is allowed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, so the description carries the burden: it discloses the temporal window semantics (matches around today), that results span leagues, and that matching is on a name fragment. It leaves the return shape and any result limits unstated, but for a read-only lookup the key behavioral traits are covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with what the tool does, followed by scope and routing. The 'both week counts are required; zero is allowed' sentence duplicates the schema's required list and property descriptions, a small redundancy.

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 3-parameter read tool with fully documented schema and no output schema, the description covers purpose, scope, matching mode, and the alternative tool. The only gap is a brief hint at what a returned match contains, which is minor here.

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%, so all three parameters are already documented. The description restates the fragment matching and the 'both week counts required; zero allowed' rule without adding format, bounds, or interaction details beyond the schema, 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 and resource ('Find recent and upcoming matches by team name'), plus scope ('around the current date across leagues') and matching mode ('partial team-name fragment'). It also names the sibling it is not (openligadb_matches_by_team_id), so an agent can distinguish it without opening a schema.

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?

Explicitly routes to openligadb_matches_by_team_id 'when you have a team id', giving a clear selection rule. It does not address other near-neighbors such as openligadb_league_team_matches, openligadb_last_team_match or openligadb_next_team_match, so the guidance is clear but not exhaustive.

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

Deploy Server

Other Tools