Crawlora MCP

sofascore_tournament_rounds

Read-only

Returns the rounds of a competition season and the current round, with each round's number, name, slug, and prefix. Use it before sofascore_round_events: cup round numbers repeat, so pass the returned slug and prefix along with the round; requires a competition id and a season id from sofascore_tournament_seasons.

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>"
    },
    "name": "sofascore_tournament_rounds"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Required. Numeric SofaScore unique-tournament (competition) id, e.g. 7 for the UEFA Champions League.
`season`	Yes	Required. Numeric SofaScore season id (from tournament-seasons), e.g. 76953.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 7, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely non-obvious behavioral context: that cup round numbers repeat and slug/prefix are needed to disambiguate. It does not discuss caching, rate limits, or failure modes, so not a full 5.

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?

Two sentences, no filler, front-loaded with purpose followed by the workflow constraint. Every clause carries information the agent needs.

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?

With an output schema present, return values need not be re-explained, and the description instead supplies the prerequisites and downstream usage. Nothing needed to call it correctly is missing.

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. The description adds provenance beyond the schema by stating the season id comes from sofascore_tournament_seasons and reinforcing that both id and season are required, which helps the agent obtain valid values.

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 the rounds of a competition season and the current round') and enumerates the returned fields (number, name, slug, prefix). An agent can distinguish it from siblings like sofascore_round_events and sofascore_tournament_seasons immediately.

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 instructs to call it before sofascore_round_events and explains the reason (cup round numbers repeat), telling the agent exactly which returned values to pass along (slug and prefix). It also names the source of the required ids (sofascore_tournament_seasons).

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

All Crawlora MCP tools Inspect

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

Need Help?