Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_trending_players

SofaScore trending players. Returns a sport's trending top players: standout performers from recent matches with the player, team, the match and that match's numbers as a snake_case metric map (rating, minutes_played, goals and more…

Instructions

SofaScore trending players. Returns a sport's trending top players: standout performers from recent matches with the player, team, the match and that match's numbers as a snake_case metric map (rating, minutes_played, goals and more; the metric set depends on the sport and position). The sport enum accepts football and basketball, the sports for which SofaScore publishes this list. Returns 404 when SofaScore has no trending players for the sport right now.

Input Schema

NameRequiredDescriptionDefault
sportYesSport key

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries full behavioral burden and does add real context: it discloses the snake_case metric-map return shape, that the metric set varies by sport and position, and that the endpoint returns 404 when no trending list exists. It omits auth, rate-limit, and freshness/refresh behavior, so it is good but not complete.

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 tool's identity, then the return content and the error condition. Three sentences, all substantive with no filler, though the metric-map parenthetical is dense.

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 must describe the return value — it does so at the entity and metric-map level — and it covers the 404 case. For a single-param, no-annotation read tool this is close to sufficient; only a note on ordering/freshness is missing.

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% and the enum values are already documented in the schema. The description restates the accepted values (football/basketball) and adds only the rationale that these are the sports SofaScore publishes the list for, which is marginal value over the schema. Baseline 3 is appropriate.

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?

The description gives a specific verb and resource ('Returns a sport's trending top players: standout performers from recent matches') and enumerates the returned entities (player, team, match, match numbers). The per-sport scope implicitly separates it from sibling tools like sofascore_team_top_players and sofascore_tournament_top_players, but no sibling is named explicitly, so it stops short of a clean 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the 'trending' scope and the recent-matches framing. There is no explicit when-to-use, when-not-to-use, or alternative named (e.g., team- or tournament-level top-player tools in the same family). The enum and 404 note aid invocation but not selection.

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