Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

livescore_competitions

Fetch English competition pages for soccer, hockey, basketball, tennis, and cricket from public sitemaps to build or monitor a competition directory.

Instructions

LiveScore competition page directory. Returns English competition pages listed in LiveScore's public competition sitemaps plus competition-shaped pages listed in the English cricket sport sitemap. The sitemap index has dedicated competition sitemaps for soccer, hockey, basketball, and tennis; cricket discovery remains partial and dynamic.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.6

TDQS

A3.6/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 full behavioural burden. It does disclose useful scope constraints (English pages only, sitemap-indexed sources, cricket coverage partial and dynamic, dedicated sitemaps for soccer/hockey/basketball/tennis), but says nothing about return format, freshness/staleness, or whether output is paginated.

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?

Two sentences, front-loaded with the resource identity, followed by the coverage/source specifics. No filler, though the second sentence is dense and could be slightly tighter.

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 no-parameter, no-output-schema directory tool, the description covers source (sitemaps), scope (English competitions), and known coverage gaps (cricket partial). An agent has what it needs to call it; only finer points like ordering are absent.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing parameter-level to document and the description introduces no spurious parameter claims.

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 resource ('LiveScore competition page directory') and what it returns, distinguishing it as the directory/list operation versus the singular sibling livescore_competition. The sibling differentiation is implicit via the 'directory' framing rather than explicitly named, but an agent can still tell them apart.

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 implied: use this to enumerate discoverable competitions. However, there is no explicit when-to-use/when-not guidance and no reference to the sibling livescore_competition or livescore_sports to route the agent between the directory and detail/sport views.

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