Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_team_players

Retrieve a SofaScore team's full squad by numeric team id, including player names, positions, jersey numbers, birth dates, height, country, preferred foot, market value, and currency.

Instructions

SofaScore team players. Returns a team's full squad from SofaScore by team id: each player's name, position, jersey number, date of birth, height, country and preferred foot, plus SofaScore's market value estimate and its currency when available.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric SofaScore team id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden itself. It helpfully enumerates the returned fields including market value and currency, which partially substitutes for the absent output schema, but it says nothing about read-only nature, permissions, or rate limits.

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?

Front-loaded and compact at two sentences, with the field enumeration doing real work. The opening 'SofaScore team players' is a mild restatement of the name, but the rest earns its place.

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-parameter read tool with no output schema, the description covers the return shape thoroughly (names, position, jersey, DOB, height, country, foot, market value, currency). The main omission is how to acquire the team id, which is a minor gap given the tool's simplicity.

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?

Only one parameter exists and schema coverage is 100%, so the schema already documents 'id' as a numeric SofaScore team id. The description's 'by team id' adds no format or sourcing detail beyond the schema, matching the baseline for full coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (returns) and resource (a team's full squad) plus the exact fields returned. It is clear what the tool does, but it does not differentiate itself from close siblings like sofascore_team or sofascore_team_player_statistics, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage hint is 'by team id', which implies an identifier is required but never says where to obtain it or when to prefer this tool over sofascore_team, sofascore_team_events, or other roster tools. No when/when-not guidance is offered.

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