Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

openligadb_last_team_match

Fetch the last played match for a team within a specified league using league ID and team ID. Find those IDs through the OpenLigaDB league and team lookup tools.

Instructions

Get a team's last match in a league. Returns the most recently played match for one team id in one league id. Discover the league id with openligadb_leagues and the team id with openligadb_teams.

Input Schema

NameRequiredDescriptionDefault
team_idYesOpenLigaDB team id from openligadb_teams
league_idYesOpenLigaDB league id from openligadb_leagues

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description has to carry the whole load; it does disclose the key semantic that the result is a played match rather than an upcoming fixture. It does not say what happens when the team has no matches in that league, or whether the response is a single object or a list.

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?

Three short sentences, front-loaded with the purpose, then the return semantics, then the prerequisite lookups. No filler; the only redundancy is restating the id-source hints already present in the schema.

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 two-parameter read tool with no annotations and no output schema, the definition covers what it does, what 'last' means, and how to obtain both ids. Only edge-case behavior (no matches found, single vs list result) is left unaddressed.

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% and both parameters already document themselves as OpenLigaDB ids sourced from openligadb_leagues/openligadb_teams. The description repeats that provenance and adds the coupling constraint ('one team id in one league id'), which is marginally useful but not beyond the schema baseline.

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: the last played match for one team in one league. The 'most recently played' clarification distinguishes it in spirit from scheduled/next-match siblings, but it never explicitly contrasts with close siblings like openligadb_last_match 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 Guidelines3/5

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

It usefully routes the agent to openligadb_leagues and openligadb_teams for ID discovery, which is real invocation guidance. However, it gives no guidance on when to choose this over openligadb_last_match (league-wide?) or openligadb_league_team_matches, leaving the sibling decision to inference.

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