Retrieve one player's bio—position, height, market value, and current team—using a numeric player ID from credential-free public JSON.
SofaScore player detail. Returns one player's bio (position, height, market value, current team) from SofaScore's credential-free public JSON.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Numeric SofaScore player id |
Changes observed during successful MCP inspections.
v1.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It mentions 'credential-free public JSON', indicating no authentication needed. However, it does not disclose rate limits, data freshness, or how the tool handles missing fields.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence. It front-loads the tool's purpose ('SofaScore player detail') and specifies the return data concisely. No extraneous information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple single-parameter tool with no output schema or annotations, the description adequately covers purpose, source, and key output fields. It could mention that the output includes additional fields not listed, but overall it is complete enough for an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already describes the 'id' parameter as 'Numeric SofaScore player id' with 100% coverage. The description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it returns a player's bio with specific fields (position, height, market value, current team) from SofaScore's credential-free public JSON. The verb 'Returns' is explicit, and the resource is distinct from sibling tools like sofascore_team or sofascore_search.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description does not explicitly state when to use this tool versus alternatives (e.g., sofascore_search to find a player ID first). It implies usage when a player ID is available, but no guidance on prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.