Crawlora MCP

sofascore_live_events

Read-only

Returns currently live events for a sport from SofaScore's credential-free public JSON. 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. Use sofascore_event to retrieve sofaScore event detail.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sport": "<sport>"
    },
    "name": "sofascore_live_events"
  }
}

Input Schema

Name	Required	Description	Default
`sport`	Yes	Required. Sport key. One of 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. Call sofascore_sports for the list.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

changedInput schema / properties / sport / description

Previous value: -"Required. Sport key. One of football, basketball, tennis."New value: +"Required. Sport key. One of 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. Call sofascore_sports for the list."

First observedOct 5, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds genuinely useful behavior beyond them: that the data comes from 'credential-free public JSON' and that 'an empty events list is a valid response when nothing is live right now' -- preventing the agent from misreading an empty result as an error. It does not mention rate limits or pagination, so it is not exhaustive.

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?

The behavioral notes about credential-free access and the valid empty response are well front-loaded and earn their place. However, the 25-value enum list is fully duplicated in the schema, which is redundant bulk that dilutes the useful content.

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 an output schema present, the description need not explain return values, and it correctly does not. It covers purpose, the enum requirement, the empty-response edge case, and the detail-lookup sibling, leaving little an agent would need beyond the structured fields.

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 sole `sport` parameter is already documented in the schema with its full enum list. The description repeats that same enumeration and the 'call sofascore_sports' hint, adding essentially nothing beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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') with a clear scope qualifier ('currently live'). It is readily distinguishable from siblings like sofascore_scheduled_events and sofascore_trending_events without opening either schema.

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?

Explicitly routes the agent to `sofascore_event` for event detail and to the sports endpoint for the sport list, giving clear context for what this tool does not do. It stops short of stating when-not to use it (e.g. for completed/scheduled matches), so it is not a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?