Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

flashscore_player_fixtures

Flashscore player fixtures. Returns one page of an individual-sport player's upcoming matches (tennis, darts, golf, snooker and similar), soonest first, as structured events.

Instructions

Flashscore player fixtures. Returns one page of an individual-sport player's upcoming matches (tennis, darts, golf, snooker and similar), soonest first, as structured events. Football, basketball and hockey players have no event list and return an empty list; use flashscore-team-fixtures for their team. 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.7/5.0
Behavior4/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 disclose meaningful behavior: results are one page, ordered soonest first, returned as structured events, and team-sport players yield an empty list. It omits auth/permission and rate-limit context, but for a read-only fixtures endpoint those are minor.

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 sentences, each earning its place: identification, scope/sport coverage with the empty-list caveat, and the paging instruction. The most decision-relevant information (scope and sibling routing) is front-loaded.

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?

With no output schema and no annotations, the description fully covers what an agent needs: the resource it returns, the ordering, the pagination termination signal, and the routing rule to the team-fixtures sibling. Nothing essential 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 baseline is 3, but the description adds real meaning to the page parameter by describing the paging loop and the termination condition (event_count is 0), which the schema's '1-based page from 1 to 300' does not convey. The id parameter's format is left entirely to the schema.

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+scope: upcoming matches for an individual-sport player, with the covered sports enumerated (tennis, darts, golf, snooker) and the ordering (soonest first). It explicitly names flashscore_team_fixtures as the sibling that handles team sports, so an agent can distinguish the two without opening either 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?

Gives explicit when-to-use (individual-sport players), explicit when-not-to-use (football/basketball/hockey players return an empty list; use flashscore-team-fixtures instead), and operational guidance on paging (request successive pages until event_count is 0). Nothing is left to inference.

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