Crawlora MCP

sofascore_event_comments

Read-only

Returns a match's text commentary (minute, type, text, players involved, running score on goals), newest first, for one SofaScore event id. Use it for play-by-play after you have an event id from sofascore_team_events or sofascore_live_events. An empty list is valid for a live match with no lines yet; a not-found error means no commentary exists, including for unstarted matches.

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

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 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only cover readOnlyHint and openWorldHint, so the description carries the substantive burden and delivers: result ordering (newest first), the empty-list-as-success semantics, and the not-found error condition. These are exactly the behaviors an agent cannot infer from annotations or schema, and none of them contradict the declared read-only nature.

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

Conciseness5/5

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

Three sentences, each earning its place: the first defines the output, the second gives the usage trigger and id source, the third handles the two ambiguous result states. The most important information (what it returns) is front-loaded.

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-parameter read tool with an output schema and read-only annotations, the description covers everything an agent needs: the identity of the resource, how to get the required id, ordering, and both success-with-no-data and error interpretations. Nothing material is left to inference.

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 single parameter already documents its type and gives an example value (14025013). The description adds marginal value by telling the agent where to obtain the id (sofascore_team_events or sofascore_live_events), but this is provenance rather than new semantics, so the baseline 3 is appropriate.

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?

The description gives a specific verb and resource ("Returns a match's text commentary"), enumerates the payload fields (minute, type, text, players involved, running score), states the ordering (newest first) and the scope (one SofaScore event id). An agent can immediately distinguish this from sibling tools like sofascore_event_incidents or sofascore_event_statistics.

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?

It explicitly states the workflow prerequisite ("Use it for play-by-play after you have an event id from sofascore_team_events or sofascore_live_events") and then specifies both edge cases: an empty list is valid for a live match, and a not-found error means no commentary exists, including unstarted matches. There is no ambiguity about when to call this and how to interpret the outcomes.

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.