Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_event_innings

Retrieve a cricket match's innings scorecards by SofaScore match ID, covering batting, bowling, extras, partnerships, and fall of wickets; returns 404 if unavailable.

Instructions

SofaScore event innings. Returns a cricket match's innings scorecards from SofaScore. Each innings has the batting and bowling teams, runs, wickets, overs in cricket notation (18.4 is 18 overs and 4 balls), extras (wides, no balls, byes, leg byes, penalty), every batter's line (runs, balls, fours, sixes, dismissal with the bowler and fielder, fall-of-wicket score and over), every bowler's figures (overs, maidens, runs, wickets, wides, no balls), the partnerships and a derived fall-of-wickets list. Works for T20, one-day and Test matches (a Test lists up to four innings). Returns 404 when SofaScore has no innings data for the match, which includes matches that have not started and sports other than cricket.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric SofaScore cricket event (match) id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and largely succeeds: it discloses that the resource is read-only-style ('Returns'), enumerates the returned structure so the agent knows what comes back, and specifies the 404 failure condition and its causes. It omits auth requirements and rate limits, which keeps it short of 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.

Conciseness4/5

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

Front-loaded with purpose, and the dense field enumeration earns its place because there is no output schema. It is longer than typical but each clause adds return-shape information; only the 'derived fall-of-wickets list' and some field lists could be trimmed.

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?

For a single-param tool with no output schema and no annotations, the description covers purpose, payload contents down to cricket notation semantics, sport/match-format applicability, and error behavior — everything an agent needs to call and interpret it.

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?

There is one parameter with 100% schema description coverage ('Numeric SofaScore cricket event (match) id'), so the schema already explains it. The prose adds no syntax, sourcing, or lookup guidance for obtaining the id, matching the baseline 3 for high coverage.

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 a cricket match's innings scorecards from SofaScore'), and the scope (cricket innings only) cleanly separates it from the many non-cricket sofascore_* siblings like sofascore_event_statistics or sofascore_event_incidents.

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?

Clearly frames when it applies ('Works for T20, one-day and Test matches') and gives explicit exclusions (404 for matches not started and for sports other than cricket), but does not name a sibling alternative to use for those cases, so routing is implied rather than directed.

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