Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fussballde_match_calendar

Find FUSSBALL.DE matches near a five-digit postcode within a date range, optionally filtered by team type or competition kind, to view local match schedules.

Instructions

Get FUSSBALL.DE matches near a postcode. Returns the matches FUSSBALL.DE's Matchkalender lists around a five-digit postcode within a date range (default today plus six days, at most 92 days), optionally filtered by team types and competition kind. Each match includes its team type (for example D-Junioren) and league. The upstream returns at most 10 matches per request and has no paging: truncated is true when the page is full, so narrow the dates or filters to see the rest. Zero matches is a valid response.

Input Schema

NameRequiredDescriptionDefault
date_toNoLast day as YYYY-MM-DD, at most 92 days after date_from, default six days after date_from
date_fromNoFirst day as YYYY-MM-DD, default today (Europe/Berlin)
team_typesNoComma-separated team type ids such as 1,3; omit for all team types
postal_codeYesFive-digit German postcode; look one up with fussballde-postal-codes
competition_kindNoCompetition kind id; omit for all kinds

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses the upstream 10-match cap, the absence of paging, the meaning of the `truncated` flag, the 92-day maximum window, and that an empty result is valid. Missing only things like rate limits or ordering of results.

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?

Front-loaded with the purpose, then defaults, then the truncation caveat. Five sentences with essentially no filler; the only mild redundancy is repeating date defaults already 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?

No output schema exists, and the description compensates by naming the returned fields (team type such as D-Junioren, league) and the `truncated` signal. Combined with the full schema coverage, an agent has what it needs to call this correctly; only result ordering and uniqueness are unstated.

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 defaults, the 92-day cap, and the YYYY-MM-DD format are already documented in the schema and are largely restated here. The description adds little parameter meaning beyond the schema, so the baseline 3 applies.

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 with scope: 'Get FUSSBALL.DE matches near a postcode ... within a date range ... optionally filtered by team types and competition kind.' That is enough to distinguish it from most siblings, though it never names a specific alternative like fussballde_club_matches or fussballde_match_plan, so full sibling differentiation is left implicit.

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 gives useful operational guidance ('narrow the dates or filters to see the rest', 'Zero matches is a valid response'), but that is about recovering from truncation rather than about when to choose this tool over the other fussballde match tools. No explicit alternatives or exclusions are stated.

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