Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_live_events

Fetch currently live sporting events for a chosen sport, returning event data or an empty list when no matches are active.

Instructions

SofaScore live events. Returns currently live events for a sport. The sport enum accepts american-football, aussie-rules, badminton, bandy, baseball, basketball, beach-volley, cricket, darts, esports, floorball, football, futsal, handball, ice-hockey, mma, minifootball, padel, rugby, snooker, table-tennis, tennis, volleyball, and waterpolo; the sports endpoint lists them. An empty events list is a valid response when nothing is live right now.

Input Schema

NameRequiredDescriptionDefault
sportYesSport key

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.12
    • changedInput schema / properties / sport / enum
      Previous value: -[
-  "football",
-  "basketball",
-  "tennis"
-]New value: +[
+  "american-football",
+  "aussie-rules",
+  "badminton",
+  "bandy",
+  "baseball",
+  "basketball",
+  "beach-volley",
+  "cricket",
+  "darts",
+  "esports",
+  "floorball",
+  "football",
+  "futsal",
+  "handball",
+  "ice-hockey",
+  "mma",
+  "minifootball",
+  "padel",
+  "rugby",
+  "snooker",
+  "table-tennis",
+  "tennis",
+  "volleyball",
+  "waterpolo"
+]
  2. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sport / enum
      Added value: +[
+  "football",
+  "basketball",
+  "tennis"
+]
  3. Addedv1.5.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that an empty 'events' list is a legitimate response rather than an error, which prevents misdiagnosis. However, it says nothing about auth needs, rate limits, or what fields the live events contain.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and readable, but the bulk of the text is a verbatim restatement of the schema enum, which is pure duplication. The genuinely informative sentences (live scope, empty-list behavior) are short and would stand alone without the redundant enumeration.

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 single-parameter, no-output-schema tool with full schema coverage, this is nearly complete: scope, valid inputs, and the empty-result case are all covered. Missing only the shape of a returned event, which is arguably beyond its remit given there is no output schema.

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% and the enum is fully enumerated in the schema, so the description's re-listing of all 24 sport keys adds no new semantics. The only added value is the hint that sofascore_sports can be used to enumerate valid sport keys.

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: 'Returns currently live events for a sport.' The scope word 'currently live' cleanly separates it from siblings like sofascore_scheduled_events and sofascore_trending_events, though those siblings are never named.

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 by 'currently live' but there is no explicit when-to-use/when-not or comparison against the scheduled/trending variants. The pointer that 'the sports endpoint lists them' helps an agent discover valid inputs, which is useful but closer to parameter guidance than 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