Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

flashscore_player

Flashscore player profile and career. Returns a player's public profile: name, country, birth date, sport, photo and current team, plus (for team-sport players) position, age, market value, contract expiry, extra details such as height…

Instructions

Flashscore player profile and career. Returns a player's public profile: name, country, birth date, sport, photo and current team, plus (for team-sport players) position, age, market value, contract expiry, extra details such as height, and career statistics by season, team and competition grouped into league, domestic cups, international cups and national team. Players of individual sports such as tennis return the profile (and ranking text) without a career table.

Input Schema

NameRequiredDescriptionDefault
idYesEight-character Flashscore player id
slugNoOptional player slug; must match the id when supplied

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

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 full burden, and it does add useful behavioral context: the output varies by sport, with individual-sport players (e.g. tennis) returning the profile plus ranking text but no career table. It still omits any mention of auth, rate limits, or how incomplete/failed lookups behave.

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?

It is dense but front-loaded, leading with the purpose before detailing return contents and the individual-sport caveat. The long enumeration is justified by the absence of an output schema, though it could be slightly tighter.

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?

With no output schema and no annotations, the description compensates well by describing exactly what the response contains and how it differs for team vs individual sports. The main gap is the lack of any when-to-use framing relative to sibling player tools.

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%, so the 'id' (eight-character player id) and optional 'slug' (must match id) are already documented in the schema. The description adds no parameter-level detail beyond that, so the baseline 3 applies.

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?

The description opens with a specific verb+resource ('Returns a player's public profile') and enumerates the exact fields and career-stat grouping, so an agent knows precisely what it yields. It does not, however, name or contrast itself against sibling player tools like flashscore_player_fixtures or flashscore_player_transfers that could also seem relevant when a player id is in hand.

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?

There is no explicit when-to-use guidance or mention of alternatives among the many flashscore_player_* siblings. Usage is only implied by the fact that a required 'id' is accepted, so an agent gets no routing help.

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