Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

sofascore_event_comments

Fetch match text commentary from SofaScore for football and basketball, including minute, event type, players, and running score, ordered newest first. Use event ID; empty comments mean no lines yet.

Instructions

SofaScore event commentary. Returns a match's text commentary (minute, type, text, and the players involved, plus the running score on scoring lines) from SofaScore, newest first. Works for football and basketball matches that have commentary. An empty comments list is a valid response (a live match with no lines yet). Returns 404 when SofaScore has no commentary for the match, which includes matches that have not started.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric SofaScore event (match) id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4/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 does well: it discloses newest-first ordering, that an empty comments list is a valid live-match state, and that a 404 signals no commentary including unstarted matches. It omits auth/rate-limit details, but the return and error semantics are well covered.

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?

Front-loaded with the core purpose, then progressively adds output fields, applicability, and edge cases. Every sentence carries information; nothing is redundant.

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?

For a simple one-parameter read tool with no output schema, the description explains both the shape of returned commentary and the empty/404 conditions, leaving little ambiguity. Complete enough to call correctly without external context.

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 sole id parameter is already documented as a numeric SofaScore event id. The description adds no id format or syntax detail 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (returns) and resource (a match's text commentary) and enumerates the returned fields (minute, type, text, players, score). It does not explicitly name a sibling alternative, but the resource is distinct from surrounding sofascore_event_* tools, so an agent can identify it without opening the 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 clear context on applicability: works for football and basketball matches that have commentary, and clarifies that empty results and 404s are expected for matches with no commentary (including not-started matches). It stops short of contrasting with alternative tools, but the when-it-works guidance is strong.

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