Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

flashscore_player_results

Flashscore player results. Returns one page of an individual-sport player's finished and in-progress matches (tennis, darts, golf, snooker and similar), newest first, as structured events with start time, stage, both sides, score and…

Instructions

Flashscore player results. Returns one page of an individual-sport player's finished and in-progress matches (tennis, darts, golf, snooker and similar), newest first, as structured events with start time, stage, both sides, score and competition. Competition blocks carry tournament_id and tournament_stage_id for the tournament endpoints. Football, basketball and hockey players have no event list and return an empty list, use flashscore-player-match-log for those. Request successive pages until event_count is 0.

Input Schema

NameRequiredDescriptionDefault
idYesEight-character Flashscore player id
pageNo1-based page from 1 to 300; defaults to 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4.8/5.0
Behavior5/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 so: it discloses sort order ('newest first'), the exact result shape (start time, stage, both sides, score, competition), an important edge case (team-sport players return an empty list), and a pagination termination condition. This is rich behavioral context beyond anything structured fields provide.

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 with the purpose, then return shape, then routing, then pagination — a logical order. The opening 'Flashscore player results.' mildly restates the name, but every subsequent sentence is dense and earns its place.

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 describe returns, which it does in detail (fields, ordering, competition ids for tournament endpoints). Combined with the empty-list edge case and pagination guidance, an agent has everything needed to call and consume this tool correctly.

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 id and page are already documented, establishing a baseline of 3. The description adds real meaning for the page parameter by explaining the iteration model ('request successive pages until event_count is 0') rather than leaving it as a bare 1-300 integer.

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 and precisely scopes it: 'one page of an individual-sport player's finished and in-progress matches (tennis, darts, golf, snooker and similar)'. It enumerates the returned event fields and names the sibling to use instead for team sports, so an agent can distinguish it without opening any schema.

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

Usage Guidelines5/5

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

Explicit when/when-not routing: individual sports return events, while 'Football, basketball and hockey players have no event list and return an empty list, use flashscore-player-match-log for those.' It also gives pagination guidance ('request successive pages until event_count is 0').

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