Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_round_events

Fetch fixtures for one competition round by tournament id, season, and round; add slug and prefix for knockout or named cup rounds to avoid 404s.

Instructions

SofaScore round fixtures. Returns fixtures for one round of a competition season. Get id from search or category-tournaments, season from tournament-seasons, and the round values from tournament-rounds. Round numbers are not unique in cups, and knockout or named rounds return 404 unless the round's slug is passed (plus its prefix when tournament-rounds lists one): the UEFA Champions League has a qualifying and a league-phase round 1, and a playoff round 636 both with the Qualification prefix and without. Plain numbered league rounds need only round. slug is lowercase letters, digits, and hyphens (up to 64 characters); prefix is letters, digits, spaces, and hyphens (up to 64 characters) and is only valid together with slug.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric SofaScore unique-tournament (competition) id
slugNoRound slug from tournament-rounds, for example round-of-16; required for knockout and named cup rounds
roundYesRound number
prefixNoRound prefix from tournament-rounds, for example Qualification; only valid together with slug
seasonYesNumeric SofaScore season id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.12
    • addedInput schema / properties / prefix
      Added value: +{
+  "description": "Round prefix from tournament-rounds, for example Qualification; only valid together with slug",
+  "type": "string"
+}
    • addedInput schema / properties / slug
      Added value: +{
+  "description": "Round slug from tournament-rounds, for example round-of-16; required for knockout and named cup rounds",
+  "type": "string"
+}
  2. Addedv1.5.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses that round numbers are non-unique in cups and that such rounds return 404 unless slug (and possibly prefix) is supplied, with a concrete UEFA Champions League example. This is non-obvious failure-mode disclosure that goes well beyond the schema.

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 core behavior ('SofaScore round fixtures') and the sourcing/rounding rules follow logically. It is dense but earns most sentences; the extended UEFA example is justified by the ambiguity it resolves, though it could be tightened slightly.

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?

There is no output schema, so the description would ideally say a bit more about the returned fixture shape, but as a fixture-listing tool the one-line return statement plus rich identifier/validation guidance covers what an agent needs to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it documents the conditional dependency (prefix is only valid together with slug), the format constraints for slug/prefix, and where each identifier originates. It stops short of elaborating round semantics beyond what the schema states, so it is not a full 5.

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 fixtures for one round of a competition season'), and the scope word 'round' distinguishes it from sibling fixture-list tools like sofascore_season_events and sofascore_tournament_rounds. An agent can identify what it fetches 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 Guidelines5/5

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

Explicitly routes the agent to the prerequisite tools (search, category-tournaments, tournament-seasons, tournament-rounds) for each identifier, and states the exact condition that selects slug/prefix versus plain round: knockout or named cup rounds need slug, numbered league rounds need only round. 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.

Deploy Server

Other Tools