Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_tournament_winners

SofaScore past winners of a competition. Returns one page (10 seasons, newest first) of a competition's past winners: the year, the season id and the winning team or player.

Instructions

SofaScore past winners of a competition. Returns one page (10 seasons, newest first) of a competition's past winners: the year, the season id and the winning team or player. Follow has_next_page and pass page (zero-based) for older seasons; a page past the last one and an unknown competition both answer 404. Get id from search; the returned season_id works with every season-scoped endpoint.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric SofaScore unique-tournament (competition) id
pageNoZero-based page number. Defaults to 0

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses page size (10 seasons), ordering (newest first), the fields returned, 404-on-exhausted and 404-on-unknown behavior, and the reuse value of season_id. It does not state rate limits or auth needs, keeping it short of 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?

Three dense sentences, front-loaded with purpose, then pagination, then id sourcing. No filler; every clause conveys actionable information.

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 2-param paginated list endpoint with no output schema, the description covers return shape, ordering, page size, termination behavior, error semantics, and the id provenance rule. An agent has everything needed to call it correctly.

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% (id and page both documented), so baseline is 3. The description adds real meaning: page is zero-based, page=0 default, follow has_next_page for older seasons, and the id comes from search. This exceeds what the schema offers.

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+resource+scope: past winners of a competition, and specifies the exact return payload (year, season id, winning team/player). Clearly distinguishable from siblings like sofascore_tournament_seasons or sofascore_tournament_info.

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?

Explains pagination mechanics, 404 semantics for exhaustion and unknown ids, and how to obtain the id ('Get id from search'). Missing an explicit statement of when NOT to use it versus similar siblings such as sofascore_tournament_seasons, but the context is strong.

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