Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

openligadb_matches_by_team_id

Retrieve recent and upcoming OpenLigaDB matches for a team ID by specifying how many weeks before and after today to include.

Instructions

Find recent and upcoming matches by team id. Returns matches around the current date across leagues for an OpenLigaDB team id. Both week counts are required; zero is allowed. Use openligadb_matches_by_team for a partial name search.

Input Schema

NameRequiredDescriptionDefault
team_idYesOpenLigaDB team id from openligadb_teams
weeks_pastYesNumber of weeks before today to include; zero is allowed
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/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the key behavioral trait that results are centered on the current date and span leagues, plus that both week windows are mandatory and may be zero. It says nothing about whether this is strictly a read, whether results are capped or paginated, or how they are ordered, leaving gaps a caller may care about.

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, front-loaded with the purpose, then the return-window behavior, then the sibling disambiguation. No filler or restated title.

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 read-only, three-parameter lookup with no output schema and no annotations, the description covers purpose, the temporal window semantics, and the primary alternative. What's missing is minor: expected result shape/ordering and whether windows are cumulative with league filtering.

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 (team_id, weeks_past, weeks_future) are already documented, including that zero is allowed. The description's restatement of required-ness adds only marginal value 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 matches by team id) plus the scope of the result (matches around the current date across leagues). It explicitly distinguishes itself from the sibling `openligadb_matches_by_team`, which is an id-vs-name distinction an agent can act on immediately.

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 routing guidance for the most confusable sibling: use `openligadb_matches_by_team` for a partial name search. It does not address other plausible alternatives such as `openligadb_last_team_match`, `openligadb_next_team_match`, or `openligadb_league_team_matches`, so the when-not coverage is partial rather than complete.

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