Crawlora MCP

sofascore_event_innings

Read-only

Returns a cricket match's innings scorecards for one SofaScore event id: runs, wickets, overs, extras, every batter's line with dismissal, bowler and fielder, bowling figures, partnerships and the fall of wickets. Use it for T20, one-day and Test scorecards after finding the event id with sofascore_live_events or sofascore_search; a not-found error means no scorecard exists, including for unstarted matches and other sports.

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_innings"
  }
}

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.

AddedOct 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond that: the not-found error semantics and the sports/start-state conditions under which no scorecard exists. It stops short of discussing pagination or partial-data behavior, but the output schema covers the return shape.

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 resource and its richest content list, followed by usage routing and error semantics. The long enumeration of scorecard fields is justified for a data-retrieval tool, though it is dense enough to be slightly heavy for a single sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema available, the description need not explain return values, and it covers everything else an agent needs: the sport scope, the prerequisite id lookup, sibling alternatives, and failure conditions. Complete for a single-parameter read tool.

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 coverage is 100% and the single parameter is fully documented with an example (14025013). The description only reinforces that it takes 'one SofaScore event id' without adding syntax or format detail beyond the schema, so the baseline of 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 a precise resource (a cricket match's innings scorecards), then enumerates the exact contents (runs, wickets, overs, extras, batter lines, bowling figures, partnerships, fall of wickets). This is clearly distinguishable from sibling tools like sofascore_event_statistics or sofascore_event_lineups.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly states when to use it (T20, one-day, Test scorecards), the prerequisite workflow (find the event id via sofascore_live_events or sofascore_search), and a clear negative case (a not-found error means no scorecard exists for unstarted matches and other sports). Nothing is left to inference.

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?