Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

flashscore_competitions

Flashscore competitions by sport and date. Discovers competitions present in a selected sport's score feed, including the provider competition id, label, region, canonical path, and event count.

Instructions

Flashscore competitions by sport and date. Discovers competitions present in a selected sport's score feed, including the provider competition id, label, region, canonical path, and event count. This is the active feed-date inventory, not an archive of inactive or historical seasons.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sportYesSport key
day_offsetNoDays from today; -7 to 7; defaults to 0

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.12
    • changedInput schema / properties / sport / enum
      Previous value: -[
-  "football",
-  "tennis",
-  "basketball",
-  "hockey",
-  "golf",
-  "formula-1",
-  "baseball",
-  "snooker",
-  "american-football",
-  "aussie-rules",
-  "badminton",
-  "bandy",
-  "beach-soccer",
-  "beach-volleyball",
-  "boxing",
-  "cricket",
-  "cycling",
-  "darts",
-  "esports",
-  "field-hockey",
-  "floorball",
-  "futsal",
-  "handball",
-  "horse-racing",
-  "kabaddi",
-  "mma",
-  "motorsport",
-  "netball",
-  "pesapallo",
-  "rugby-league",
-  "rugby-union",
-  "table-tennis",
-  "volleyball",
-  "water-polo",
-  "winter-sports"
-]New value: +[
+  "football",
+  "tennis",
+  "basketball",
+  "hockey",
+  "golf",
+  "formula-1",
+  "baseball",
+  "snooker",
+  "american-football",
+  "aussie-rules",
+  "badminton",
+  "bandy",
+  "beach-soccer",
+  "beach-volleyball",
+  "boxing",
+  "cricket",
+  "cycling",
+  "darts",
+  "esports",
+  "field-hockey",
+  "floorball",
+  "futsal",
+  "handball",
+  "horse-racing",
+  "kabaddi",
+  "mma",
+  "motorsport",
+  "netball",
+  "pesapallo",
+  "rugby-league",
+  "rugby-union",
+  "table-tennis",
+  "volleyball",
+  "water-polo",
+  "winter-sports",
+  "moto-racing",
+  "ski-jumping",
+  "alpine-skiing",
+  "cross-country-skiing",
+  "biathlon"
+]
  2. Addedv1.17.5

TDQS

A4.3/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 disclose meaningful behavior: it is the active feed-date inventory rather than an archive, and it enumerates the returned fields (provider id, label, region, canonical path, event count). It omits any note on rate limits or freshness/latency, which is the only gap for a read-only discovery tool.

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 tight sentences, front-loaded with the verb and scope, then the return contents, then the disambiguating constraint. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, no-output-schema tool, the description supplies the return-field inventory that the missing output schema would otherwise convey, plus the active-vs-archive semantics. Nothing needed to call it correctly is absent.

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%, including an enum for sport and a documented range/default for day_offset, so the schema already does the heavy lifting. The description only gestures at the sport+date dimensions and adds no syntax or format detail beyond the schema; baseline 3 is appropriate.

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 (discovers) and resource (competitions) scoped by sport and date, and names the exact data returned. The closing sentence distinguishes it from historical-archive siblings (e.g. flashscore_tournament_seasons), so an agent can select it without opening another 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?

Clearly frames the use case: competitions present in a selected sport's live score feed for a given date. It explicitly excludes the archive case ("not an archive of inactive or historical seasons"), giving useful when-not guidance, though it does not name a specific alternative sibling to redirect to.

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