Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_player

Retrieve a SofaScore player's profile by numeric ID, including name, position, jersey number, birth date, height, preferred foot, country, market value, and current team.

Instructions

SofaScore player detail. Returns one SofaScore player by numeric id: name, short name, position, jersey number, date of birth, height, preferred foot, country, market value and currency, and the current team. deceased is true for historical players. An unknown or malformed id returns an upstream error.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric SofaScore player id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does a fair job: it discloses the returned field set (substituting for the missing output schema), explains the `deceased` flag for historical players, and states the failure mode ('unknown or malformed id returns an upstream error'). Auth, rate limits, and full payload structure 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core behavior and then the field list and edge case. No filler; each sentence carries information.

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 single-param, no-output-schema lookup, the description adequately covers what is returned and how failures behave. It is slightly short on routing context (how to obtain the id) and does not fully enumerate the response shape, but nothing critical is missing.

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 baseline is 3, but the description adds real value beyond the schema by reinforcing that the id is numeric and warning that a malformed id causes an upstream error - an operational constraint on the single parameter that the schema does not express.

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 ('Returns one SofaScore player by numeric id') and enumerates the profile fields returned, which cleanly separates this profile lookup from id-finding siblings (sofascore_search) and from statistical siblings like sofascore_player_season_statistics or sofascore_player_transfers.

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: the tool needs a numeric player id, so the agent can infer it is called after obtaining an id from search. There is no explicit when-to-use-vs-alternatives guidance (e.g., 'use sofascore_search first to resolve a name to an id') and no exclusions.

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