Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

sofascore_round_events

Read-only

List SofaScore fixture rows for a competition season and round. Get id from search, season from sofascore_tournament_seasons, and round locators from sofascore_tournament_rounds. Numbered league rounds need round alone; named or knockout rounds also require the returned slug, plus prefix when provided. prefix is valid only with slug because round numbers can repeat across phases. Use sofascore_event to inspect one returned fixture.

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>",
      "season": "<season>",
      "round": "<round>"
    },
    "name": "sofascore_round_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRequired. Numeric SofaScore unique-tournament (competition) id, e.g. 17 for the Premier League.
slugNoOptional. Round slug from sofascore_tournament_rounds, e.g. round-of-16. Required for knockout and named cup rounds, which return 404 without it; leave empty for plain numbered rounds.
roundYesRequired. Round number, e.g. 1. Cup rounds can share a number, so pass the slug (and prefix) that sofascore_tournament_rounds returns for the round.
prefixNoOptional. Round prefix from sofascore_tournament_rounds, e.g. Qualification. Only valid together with slug; use it when a round number and slug exist both with and without a prefix.
seasonYesRequired. Numeric SofaScore season id (from tournament-seasons), e.g. 76986.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds valuable behavioral detail: knockout/named rounds require slug or return 404, prefix is valid only with slug, and round numbers can repeat across phases. This exceeds what annotations cover, though it omits pagination or rate-limit behavior.

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?

Four sentences, front-loaded with the core purpose, followed by sourcing, special-case rules, and the alternative tool. Every sentence adds essential information with no redundancy.

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?

Given an output schema and annotations that cover safety and openness, the description supplies all missing context: parameter sources, conditional logic for slug/prefix, and the correct alternative for single-fixture needs. Nothing needed to invoke correctly is absent.

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 description coverage is 100%, so baseline is 3. The description adds meaningful sourcing guidance ('Get id from search, season from sofascore_tournament_seasons, and round locators from sofascore_tournament_rounds') and explains the interdependent relationship between slug and prefix, going beyond the schema text.

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 states a specific verb and resource: 'List SofaScore fixture rows for a competition season and round.' It distinguishes itself from siblings by naming sofascore_event for single-fixture inspection and pointing to the source tools for required parameters.

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?

It provides clear context (competition season and round) and explicitly routes to sofascore_event for a single fixture. It also distinguishes numbered from named/knockout rounds, but does not mention when to prefer this over other list tools like sofascore_season_events.

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

All Crawlora MCP toolsInspect
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.

Resources