Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_player_ratings

SofaScore player match ratings for a season. Returns a player's rating in every match of one competition season, newest first, with the opponent, home or away and the match.

Instructions

SofaScore player match ratings for a season. Returns a player's rating in every match of one competition season, newest first, with the opponent, home or away and the match. The type enum accepts overall, home, away, regular_season and playoffs and defaults to overall; football seasons answer overall and NBA seasons answer regular_season and playoffs (the types a season offers are listed by player-statistics-seasons). Returns 404 when SofaScore has no ratings of that type for the combination.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric SofaScore player id
typeNoStatistics view
seasonYesNumeric SofaScore season id from player-statistics-seasons
tournament_idYesNumeric SofaScore unique-tournament (competition) id from player-statistics-seasons

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations the description carries the full burden, and it delivers useful behavior: results are ordered newest first, each row includes opponent, home/away and the match, and a 404 is returned when SofaScore has no ratings of that type. It omits permissions, rate limits and pagination behavior, keeping it below 5.

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?

Two sentences, front-loaded with what is returned and followed by the enum rules and error case. Dense but every clause earns its place; the enum sentence is long but informative rather than padded.

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?

For a 4-parameter tool with no output schema and no annotations, the description covers return shape, ordering, key fields, valid enum values and the 404 failure mode. Only auth/permission and pagination details are missing, which is a minor gap.

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 schema already documents all four parameters. The description nevertheless adds genuine meaning beyond the terse schema text ('Statistics view') by explaining which enum values apply per sport, the default, and where valid season/tournament ids come from.

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 precise verb and resource: 'Returns a player's rating in every match of one competition season.' It also scopes the result set (ratings only, one competition season) which separates it from sibling stats tools like sofascore_player_season_statistics or sofascore_player_events.

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 real context for choosing the tool's mode: the type enum defaults to overall, football seasons answer overall, and NBA seasons answer regular_season/playoffs, with player-statistics-seasons named as the source of valid types. It does not explicitly compare against alternative sibling tools, so it stops short of 5.

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