Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_player_attributes

SofaScore player attributes and characteristics. Returns a football player's attribute scores (0 to 100) for the current year and up to three earlier years (year_shift 0 to 3), the average scores for the player's position, and the…

Instructions

SofaScore player attributes and characteristics. Returns a football player's attribute scores (0 to 100) for the current year and up to three earlier years (year_shift 0 to 3), the average scores for the player's position, and the player's characteristics: playing positions plus strengths and weaknesses, each with SofaScore's numeric code, a key and name such as finishing or aerial duels, and a rank. Outfield players carry attacking, technical, tactical, defending and creativity scores; goalkeepers carry saves, anticipation, ball_distribution, aerial and tactical. Combines two SofaScore requests. Returns 404 for players without attribute overviews, which includes non-football players.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric SofaScore player id

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 full burden and does well: it discloses that it combines two SofaScore requests, that it covers up to three prior years, and crucially that it returns 404 for players lacking attribute overviews including non-football players. It omits auth/rate-limit details, but for a read tool the disclosed behavior is substantial.

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?

The description is dense but front-loaded, opening with the resource and then the returned fields, with no filler sentences. It is slightly long, but each sentence conveys concrete content about what is returned or how the tool behaves.

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?

There is no output schema, so the description must explain the return values, and it does so thoroughly: numeric code/key/name/rank for strengths and weaknesses, distinct outfield vs goalkeeper attribute sets, position averages, and the 404 edge case. An agent has enough to call and interpret results correctly.

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% for the single `id` parameter, so the schema already documents the required input and the baseline is 3. The description adds output-shape meaning (score ranges, outfield vs goalkeeper fields) but references a `year_shift` parameter that is absent from the input schema, which does not clarify the actual parameter.

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?

The description names a specific resource (SofaScore player attribute scores and characteristics) and clearly states what is returned: attribute scores 0-100 for the current year plus earlier years, position averages, and strengths/weaknesses. It is distinguishable from siblings like sofascore_player (basic profile) and sofascore_player_statistics_seasons, because it explains the unique combined content it provides.

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 implied rather than explicit: the description gives a strong condition in 'Returns 404 for players without attribute overviews, which includes non-football players,' which tells the agent when the tool will not work. However, it never names an alternative tool or says explicitly when to prefer this over sofascore_player or sofascore_player_statistics_seasons.

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