Crawlora MCP

sofascore_event_incidents

Read-only

Returns one match's goal, card, substitution, and period timeline from SofaScore's credential-free public JSON. An empty incidents list is a valid response before kickoff. id: Required. Numeric SofaScore event (match) id, e.g. 14025013. 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": {
      "id": "<id>"
    },
    "name": "sofascore_event_incidents"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Required. Numeric SofaScore event (match) id, e.g. 14025013.

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.

First observedOct 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real behavioral detail beyond that: the data comes from credential-free public JSON (no auth needed) and an empty list is a legitimate pre-kickoff result, which heads off a false 'no data' conclusion. It omits ordering/rate-limit traits.

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?

Three tight sentences, purpose front-loaded, edge case second, sibling pointer last. The only redundancy is the 'id: Required...' sentence, which merely restates the schema field.

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, return values need not be explained, and the description still covers purpose, data source, the empty-list edge case, and a sibling pointer. Enough for correct invocation, though it could say more about how incidents relate to the event-detail call.

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 required 'id' with its format and example is already fully documented in the schema. The description repeats that text verbatim and adds no new syntax or constraint, 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 ('Returns') and the exact resource payload (goal, card, substitution, and period timeline), which cleanly separates it from near siblings like sofascore_event_highlights, sofascore_event_comments, and sofascore_event_lineups. It also names the parent tool sofascore_event, so an agent can position it without opening a 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?

Gives a concrete context clue ('An empty incidents list is a valid response before kickoff') and names an alternative (sofascore_event) for event detail. It stops short of stating when NOT to use this tool or explicitly ordering the two calls, so it is clear context rather than full when/when-not guidance.

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?