Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

livescore_search

Search LiveScore teams, competitions, and regions using a free-text query or browse current sections by sport. Returns JSON results per section.

Instructions

Search LiveScore teams, competitions, and regions. Searches the public LiveScore index for a free-text term, or browse its current team, competition-stage, and region-category sections with an empty query. Results are dynamic, limited per section, and are not a complete historical competition directory. Use /livescore/sports to discover all supported sport tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoOptional results per section (1 to 100). Defaults to 10 for a text query or 50 when query is empty.
queryNoOptional free-text team, competition, or region term (up to 100 characters). Omit or leave empty to browse current results.
sportYesLiveScore sport token

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.6

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden and does disclose useful behavior: results are dynamic, per-section limited, and explicitly not a complete historical competition directory. It also notes the index is public. It stops short of auth/rate-limit or response-format detail, but the disclosures given are meaningful.

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 core purpose, then scope limitations, then the sports-token pointer. Four sentences, each carrying information; only mild redundancy between the search and browse phrasing prevents a 5.

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 and no annotations, the description supplies what an agent needs: the two invocation modes, valid sport tokens pointer, and the caveat that results are partial and dynamic. Adequate for a three-parameter search tool, though nothing is said about result shape beyond section limitation.

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 all three parameters (sport, query, limit) are already documented, including the default limit behavior for empty vs. non-empty queries. The description echoes the empty-query browse semantics but adds no syntax or format detail beyond the schema, so 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: search LiveScore teams, competitions, and regions, with the dual mode (free-text search vs. empty-query browse) made explicit. It does not differentiate itself from close siblings like livescore_team, livescore_competition, or livescore_competitions, which keeps it short of a 5.

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 explains when to pass a query (free-text search) versus leaving it empty (browse section listings), and routes the agent to /livescore/sports to discover valid sport tokens. No explicit when-not-to-use or sibling comparison beyond that pointer.

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