Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fussballde_match

Fetch a single FUSSBALL.DE match by ID to get teams, competition, date, kick-off time, venue, scores, officials, goals, and timeline events; unpublished fields are omitted.

Instructions

Get a FUSSBALL.DE match. Returns one match: teams, competition, date, kick-off time, venue, score and half-time score, match number and matchday, officials, goals with minutes and timeline events such as substitutions. Fields the match has not published (for example a future match's score) are omitted.

Input Schema

NameRequiredDescriptionDefault
match_idYesMatch id from fussballde-matchday or fussballde-match-plan

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does add useful context: it lists the returned fields and explicitly notes that unpublished fields, such as a future match's score, are omitted. That omission behavior is important for interpreting incomplete results. It does not describe errors, authentication, or rate limits, but for a simple read-only lookup it is reasonably transparent.

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?

The description is two sentences, front-loaded with the core purpose, and every clause adds useful information about returned fields or omissions. There is no redundant or filler content.

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 single-parameter lookup with no output schema, the description is largely complete because it enumerates the key return fields and explains omission behavior. The match_id source is handled by the schema rather than the description, which is acceptable given its full description coverage.

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?

The input schema has 100% description coverage for the sole match_id parameter, including its source in fussballde-matchday or fussballde-match-plan. The description itself adds no parameter-level meaning, so the baseline score of 3 is appropriate.

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?

The description states a specific verb and resource ("Get a FUSSBALL.DE match") and clarifies that it returns exactly one match, which distinguishes it from list-oriented siblings such as fussballde_matchday and fussballde_match_plan. It is clear what the tool does, though it does not explicitly name or differentiate against other single-match tools from other providers.

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?

Usage is implicit: an agent can infer this tool is for retrieving details of a known match, but the description does not state when to use it versus alternatives such as fussballde_matchday or fussballde_match_plan. It also does not repeat the schema's guidance that the match_id comes from those sibling tools.

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