Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

livescore_competition

Fetch public competition or stage page data and its visible sections using an /en/ path; discover sitemap-listed sport paths, including cricket stage pages.

Instructions

LiveScore competition page and section data. Returns public competition or stage page data and its visible sections. Competition ids and tabs vary by sport; discover English sitemap-listed paths, including cricket stage pages, with /livescore/competitions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesThree to five lowercase path segments following /en/, such as football/england/premier-league or football/england/premier-league/standings

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses that data is 'public' and that sections are 'visible,' and warns that ids/tabs vary by sport, but says nothing about rate limits, pagination, or what 'sections' actually contain.

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 tight sentences with the return content front-loaded and the input-discovery hint last. No filler, though the second and third sentences could be merged for tighter structure.

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

Completeness3/5

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

For a single-parameter read tool with no annotations and no output schema, the description covers what is returned and how to find valid paths, but leaves the response shape and section structure entirely unspecified, which limits an agent's ability to know what it will get back.

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%, so the path syntax and examples are already fully documented in the schema. The description adds only the observation that ids and tabs vary by sport, which is marginal semantic value 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 and resource: it 'returns public competition or stage page data and its visible sections.' It partially differentiates itself by mentioning 'stage pages' and referencing the discovery tool, but does not clearly distinguish its role from the very similarly named sibling livescore_competitions.

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 implicitly tells the agent to obtain valid inputs via /livescore/competitions, which is useful prerequisite guidance, and notes that ids/tabs vary by sport. However, it never states when to use this versus alternatives like livescore_match or livescore_scores.

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