Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_round_events

Fetch a single round of fixtures from SofaScore by passing competition ID, season ID, and round number. Use it to retrieve match schedules for one competition season round.

Instructions

SofaScore round fixtures. Returns fixtures for one round of a competition season from SofaScore's credential-free public JSON. Get id from search and season from tournament-seasons.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric SofaScore unique-tournament (competition) id
roundYesRound number
seasonYesNumeric SofaScore season id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It notes the tool uses 'SofaScore's credential-free public JSON', indicating no authentication is required and it is a read operation. However, it does not disclose potential error handling, rate limits, or response structure, which limits transparency.

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?

The description is three sentences, each serving a distinct purpose: naming the tool, describing output, and providing parameter sourcing advice. No redundant words or unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema, the description does not explain the return format (e.g., list of events with what fields). It adequately covers tool purpose and parameter origin, but lacks details on what 'fixtures' entails or error conditions, leaving some ambiguity.

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. The description adds value by telling the agent to obtain `id` from search and `season` from tournament-seasons, which is operational guidance beyond the schema's numeric descriptions. This enriches parameter meaning.

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 clearly states the tool returns fixtures for one round of a competition season, using specific verbs ('Returns') and resources ('fixtures'). It distinguishes from sibling tools like sofascore_event (single event) and sofascore_standings by focusing on round-level data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description provides guidance on obtaining parameter values ('Get `id` from search and `season` from tournament-seasons'), implying usage context. However, it does not explicitly state when to use this tool versus alternatives like sofascore_standings or sofascore_live_events, leaving potential confusion among many sibling tools.

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