Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

flashscore_tournament_standings

Get Flashscore competition standings by supplying the competition path. Select a view (overall, home, away, form) to receive the raw delimited table.

Instructions

Flashscore competition standings table. Returns a competition-level table feed independent of a match id. Discover the stage-specific view values with flashscore-tournament-standings-views. Data remains in Flashscore's raw delimited format.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesRelative Flashscore competition path from flashscore-navigation or flashscore-competitions; omit /standings/
viewNoView returned by flashscore-tournament-standings-views; defaults to overall

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.6/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. It does disclose that the data 'remains in Flashscore's raw delimited format,' which is useful, but it does not describe pagination, response container, size limits, or other behaviors beyond 'table feed.'

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 short sentences front-load the core purpose and keep the raw-format warning near the end. Slight redundancy exists between 'competition standings table' and 'competition-level table feed,' but there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with two well-documented parameters and no output schema, the description names the output format but leaves ambiguity around what the raw delimited data represents and how the returned table is structured. It is adequate for invoking the tool but not fully self-contained.

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% and already explains the path and view parameters. The description reinforces that view values come from flashscore-tournament-standings-views, but adds no new parameter semantics beyond 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?

Description states a specific verb and resource: 'Returns a competition-level table feed' of Flashscore competition standings. The phrase 'independent of a match id' explicitly differentiates it from the sibling flashscore_match_standings.

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

Usage Guidelines3/5

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

The description implies when the tool is appropriate—competition-level standings rather than match-specific data—and points to flashscore-tournament-standings-views for view values. It does not explicitly state when to prefer alternatives such as flashscore_match_standings or what preconditions must hold.

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