Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

sofascore_tournament_rounds

Instructions

SofaScore competition season rounds. Returns the rounds of a competition season and the current round. Round numbers are not unique in cups: the UEFA Champions League has both a qualifying and a league-phase round 1, and the same playoff round number with and without a prefix. To fetch a round's fixtures, pass its round to round-events together with its slug and, when present, its prefix; knockout and named rounds return 404 from round-events without the slug. Plain numbered rounds (a league's round 1 to 38) have no slug. Get id from category-tournaments or search and season from tournament-seasons. Returns 404 when SofaScore has no rounds for the season (for example a season that has not started).

Input Schema

Name	Required	Description	Default
`id`	Yes	Numeric SofaScore unique-tournament (competition) id
`season`	Yes	Numeric SofaScore season id from tournament-seasons

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.12Oct 13, 2026

TDQS

A4.5/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 that round numbers are non-unique in cups, that slug/prefix are sometimes required, that plain numbered rounds have no slug, and that 404 signals no rounds for the season. It stops short of describing pagination or the exact response shape, but the behavioral disclosure is rich.

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?

The description is dense but front-loaded, leading with what it returns before the caveats. Every sentence carries operational information (slug/prefix rules, 404 behavior, id/season sourcing), though it runs long and could tighten the cup-round explanation.

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?

With no output schema, the description adequately explains that it returns rounds plus the current round and when a 404 occurs. It covers the tricky edge cases an agent needs, leaving only minor gaps around exact return structure.

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 baseline is 3, but the description adds real value by explaining where each parameter comes from (id from category-tournaments or search; season from tournament-seasons). It also introduces the derived `round`/`slug`/`prefix` fields the agent will need downstream, going beyond the two schema fields.

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 opens with a specific verb and resource ('Returns the rounds of a competition season and the current round') and distinguishes this tool from siblings by naming round-events, tournament-seasons, and category-tournaments. An agent can tell exactly what this returns and how it differs from adjacent SofaScore tools.

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 gives an explicit workflow: get `id` from category-tournaments or search, get `season` from tournament-seasons, then pass a round's `round`/`slug`/`prefix` to round-events. It even states the failure mode (round-events returns 404 without the slug) so the agent knows the sequencing constraint.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

sofascore_tournament_rounds

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools