Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

flashscore_tournament_seasons

Flashscore tournament archive seasons. Lists the seasons and winners (both players for doubles) from a public competition archive page. Discover archive paths through flashscore-navigation or flashscore-competitions.

Instructions

Flashscore tournament archive seasons. Lists the seasons and winners (both players for doubles) from a public competition archive page. Discover archive paths through flashscore-navigation or flashscore-competitions. Each returned results_path and fixtures_path can be passed to flashscore-tournament-events to retrieve season event feeds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesRelative Flashscore competition archive path ending in /archive/

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/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 behavioral burden. It conveys that this is a read/list operation over a public archive and describes the shape of the output (seasons, winners, doubles pairs, results_path/fixtures_path), but says nothing about authentication, rate limits, pagination, or explicitly that it is non-destructive. Useful but incomplete for an unannotated tool.

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?

Three tight sentences with the core purpose front-loaded, followed by prerequisite and downstream chaining. The opening fragment reads slightly like a title, but no sentence is wasted.

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?

No output schema exists, and the description adequately covers what is returned and how the outputs chain into other tools, which is the key information an agent needs. It is only lightly short on operational details like auth or pagination, which are minor for a public read endpoint.

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% and the schema already documents the path format, so the baseline is 3. The description adds real value beyond the schema by telling the agent how to source a valid value (via flashscore-navigation or flashscore-competitions), which is non-obvious for a constructed archive path.

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 (lists) and resource (seasons and winners from a competition archive page), and explicitly separates itself from siblings by naming flashscore-navigation/flashscore-competitions for path discovery and flashscore-tournament-events for event feeds. An agent can tell it apart from flashscore_tournament_events and flashscore_tournament_archive_seasons without opening a schema.

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

Usage Guidelines4/5

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

Gives clear workflow context: where to get the required path (navigation/competitions) and where to pass the returned results_path/fixtures_path (tournament-events). It does not state an explicit when-not-to-use or a hard alternative condition, so it falls short of a 5.

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