Crawlora MCP

sofascore_player_ratings

Read-only

Returns a SofaScore player's rating in every match of one competition season, newest first, with opponent, home or away and the match. Requires player id, tournament_id and season from sofascore_player_statistics_seasons; type defaults to overall (football) and can be regular_season or playoffs for the NBA. A not-found error means no ratings of that type exist.

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>",
      "tournament_id": "<tournament_id>",
      "season": "<season>"
    },
    "name": "sofascore_player_ratings"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Required. Numeric SofaScore player id, e.g. 839956.
`type`	No	Optional. One of overall, home, away, regular_season, playoffs. Defaults to overall. Football seasons answer overall; NBA seasons answer regular_season and playoffs.
`season`	Yes	Required. Numeric SofaScore season id from player-statistics-seasons, e.g. 76986.
`tournament_id`	Yes	Required. Numeric SofaScore unique-tournament (competition) id from player-statistics-seasons, e.g. 17.

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

Behavior4/5

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

Annotations already cover read-only and open-world status. The description adds behavior beyond them: results are newest-first and a not-found error specifically signals that no ratings of the requested type exist, which is genuinely useful error-handling context. Auth and rate-limit behavior remain unstated.

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?

Three front-loaded sentences that begin with the purpose and then layer params, type semantics and error meaning. Dense with no filler, though the third sentence leans on prior-tool references that keep it slightly heavier than necessary.

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?

An output schema exists, so return values need not be re-described. Given the tool's complexity, the description covers purpose, ordering, parameter sourcing and error semantics well; only auth/permission context is absent.

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 description coverage is 100% and the schema already enumerates the type values, defaults and per-sport behavior. The description largely restates the default and allowed type values plus the ID sourcing, adding little that the schema does not already provide, so baseline 3 is right.

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 a player's rating in every match of one competition season. It further specifies the output shape (opponent, home/away, the match) and ordering (newest first), which is enough to distinguish it from generic player-statistics siblings.

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?

It directs the agent to obtain id, tournament_id and season from sofascore_player_statistics_seasons, which establishes the prerequisite workflow, and clarifies which type value applies per sport. It stops short of naming explicit alternatives or when-not-to-use cases, so it is clear context rather than full routing.

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?