Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_season_events

SofaScore season fixtures and results. Returns one page (about 30 events) of every fixture or result of a competition season, with the round of each event.

Instructions

SofaScore season fixtures and results. Returns one page (about 30 events) of every fixture or result of a competition season, with the round of each event. The direction enum accepts next (upcoming fixtures) and last (finished results). Follow has_next_page to read further pages: a page past the end, a direction with no events (for example next in a finished season) and a season id that does not belong to the competition all answer 404. Get id from search and season from tournament-seasons.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric SofaScore unique-tournament (competition) id
pageNoZero-based page number. Defaults to 0
seasonYesNumeric SofaScore season id
directionYesUpcoming fixtures or finished results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral load well: it discloses page size (~30 events), that the round is included, pagination via has_next_page, and the specific 404 conditions. It omits auth/rate-limit context, so it stops short of full transparency.

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?

Front-loaded with the core purpose in the first sentence, then dense but useful detail on direction and pagination. Slightly information-heavy but each sentence earns its place.

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?

No output schema exists, so the description is responsible for return shape; it covers record count, the included round field, and pagination. Complete enough to invoke correctly, with only auth/permissions left unstated.

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 a 3 would be the floor. The description adds real value beyond the schema by stating the provenance of `id` (from search) and `season` (from tournament-seasons), which the schema does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 every fixture or result of a competition season, with the round of each event. This clearly scopes it apart from season-agnostic or team/round siblings, though it never names an alternative explicitly.

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?

Gives a concrete acquisition flow (get `id` from search, `season` from tournament-seasons) and explains the `direction` choice (next = upcoming, last = finished). Error conditions are spelled out, but there is no explicit 'when not to use this vs sibling' statement.

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