Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

sofascore_live_events

Fetch currently live football, basketball, or tennis events from SofaScore's public JSON. Returns an events list, which may be empty when no matches are live.

Instructions

SofaScore live events. Returns currently live events for a sport from SofaScore's credential-free public JSON. The sport enum accepts football, basketball, and tennis. An empty events list is a valid response when nothing is live right now.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sportYesSport key

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sport / enum
      Added value: +[
      +  "football",
      +  "basketball",
      +  "tennis"
      +]
  2. Addedv1.5.0

TDQS

A3.7/5.0
Behavior4/5

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

No annotations are present, so the description carries the full burden. It discloses that the source is credential-free (no auth needed) and that an empty events list is a valid response, which are useful behavioral details. However, it omits other traits like rate limits, response format, or pagination, preventing a 5.

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?

The description is two sentences with no unnecessary words. The primary purpose is front-loaded, followed by the parameter values and the empty-list behavior. It is highly concise and well-structured.

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?

With one parameter, no output schema, and no annotations, the description covers the purpose, parameter, and a behavioral edge case. However, it does not describe the structure of the returned events list, which would be helpful given the absence of an output schema. It is adequate but not fully complete.

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 baseline is 3. The description restates the enum values (football, basketball, tennis) which is redundant with the schema. It adds no new meaning about the parameter beyond what the schema already provides.

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?

The description clearly states the tool returns currently live events for a sport, with a specific verb and resource. It identifies the source (SofaScore public JSON) but does not explicitly differentiate from sibling tools like sofascore_round_events or sofascore_event, so it falls 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for live events ('Returns currently live events') but does not mention when not to use it or point to alternatives. It lacks explicit guidance on when to choose this over other SofaScore event tools, so it only meets the 'implied usage' level.

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