Crawlora MCP

sofascore_season_events

Read-only

Returns one page of about 30 fixtures (direction next) or results (direction last) for a whole SofaScore competition season, with each event's round. Follow has_next_page for more pages; a page past the end or a direction with no events returns not found. Use sofascore_round_events instead for a single round.

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

Input Schema

Name	Required	Description
`id`	Yes	Required. Numeric SofaScore unique-tournament (competition) id, e.g. 17 for the Premier League.
`page`	No	Optional. Zero-based page number, about 30 events per page. Defaults to 0.
`season`	Yes	Required. Numeric SofaScore season id (from tournament-seasons), e.g. 96668.
`direction`	Yes	Required. One of next (upcoming fixtures), last (finished results).

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.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the description earns credit for adding pagination mechanics (has_next_page) and edge-case behavior ('a page past the end or a direction with no events returns not found'). It does not discuss rate limits or auth, but the safety context is already carried by annotations and the output schema handles return shape.

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?

Three tightly packed sentences that lead with what is returned, then pagination/error handling, then the disambiguating alternative. Every clause carries information and there is no filler.

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?

For a paginated read tool with full schema coverage, annotations covering safety, and an output schema covering the return shape, the description supplies everything else an agent needs: page size, continuation field, empty/out-of-range behavior, and the sibling routing rule.

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

Parameters3/5

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

Schema coverage is 100%, so each parameter is already documented with examples (id, season, page, direction). The description's direction framing ('next' fixtures / 'last' results) and '~30 per page' largely restate what the schema already says, so the baseline 3 is appropriate.

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 one page of about 30 fixtures or results for a whole SofaScore competition season, with each event's round') and scopes it precisely to a season. It explicitly names the sibling it is not ('Use sofascore_round_events instead for a single round'), so an agent can separate it from the single-round tool 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?

Gives the when-to-use condition per parameter value ('direction next' = fixtures, 'direction last' = results), instructs how to continue ('Follow has_next_page for more pages'), and names the alternative plus its selecting condition ('sofascore_round_events for a single round'). Nothing material 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.

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?