Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

flashscore_match_tv

Flashscore match TV and streaming broadcasters. Returns the TV channels and streaming services listed for a match in one viewer market, with provider ids, names and website links.

Instructions

Flashscore match TV and streaming broadcasters. Returns the TV channels and streaming services listed for a match in one viewer market, with provider ids, names and website links. Listings are country specific, so pick geo from flashscore-odds-geos; an empty list means no broadcaster is listed for that market. Bookmaker promotions are not included.

Input Schema

NameRequiredDescriptionDefault
idYesEight-character Flashscore match id
geoNoViewer market country code from flashscore-odds-geos; defaults to GB

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden, and it does well: it lists what is returned (provider ids, names, website links), discloses the empty-result case, and excludes bookmaker promotions. It omits auth/rate-limit context, but for a read-only lookup that is a minor gap.

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?

Four compact sentences, front-loaded with the core purpose followed by return shape, geo sourcing, and exclusions. Each sentence contributes something and there is no filler, though it is slightly denser than strictly necessary.

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?

With no output schema, the description correctly explains the return content (channels, services, provider ids, names, links) and the empty-list case. Both parameters are documented in the schema, so nothing essential for a correct call is missing, though a note on result freshness or ordering would round it out.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds real meaning beyond the schema: it directs the agent to flashscore-odds-geos as the source of geo values, explains the default market behavior, and clarifies that an empty result is a valid 'no listing' response rather than an error.

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: it returns TV channels and streaming services for a Flashscore match in one viewer market, with provider ids, names and links. This is concrete enough for an agent to grasp the resource. It does not explicitly name a competing sibling (e.g. flashscore_match_odds or another broadcaster tool), so it stops short of full sibling differentiation.

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 operational context: pick the market via geo from flashscore-odds-geos and treat an empty list as 'no broadcaster in that market'. This tells the agent how to source the geo value. It does not spell out explicit when-not conditions, so it is clear context rather than full routing guidance.

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