Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

flashscore_tournament_draw

Fetch a Flashscore knockout stage draw by season tournament and stage IDs to get entrants, ordered rounds, slots, linked match IDs, scores, winners, and replay or empty-slot status.

Instructions

Flashscore tournament draw by season and stage. Returns one knockout stage with its entrants and ordered bracket rounds, slots, linked match IDs, scores and winners. A slot can contain replays or have no linked match yet. Use the season tournament_id and its stage_id from flashscore-tournament-archive-seasons or the competition block of an event. A stage without a published draw returns not found.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tournament_id": "<tournament_id>",
      "stage_id": "<stage_id>"
    },
    "name": "flashscore_tournament_draw"
  }
}

Input Schema

NameRequiredDescriptionDefault
stage_idYesEight-character Flashscore draw stage id
tournament_idYesEight-character Flashscore season tournament id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.3/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 well: it discloses the return shape (entrants, ordered rounds, slots, match IDs, scores, winners), notes that a slot may hold replays or have no linked match yet, and defines the empty-result behavior for unpublished draws. It never explicitly states the operation is read-only, which an agent must infer from 'Returns'/'draw'.

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?

The purpose and return contents are front-loaded, and every sentence contributes facts (return shape, replay caveat, id sourcing, not-found case). It is slightly dense and the id-sourcing sentence could be split for scanability, but there is no filler.

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?

For a two-parameter read tool with no output schema and no annotations, the description covers what is returned and the edge cases an agent needs to interpret an empty result. The only gap is the absence of an explicit read-only/mutation statement and any note on data freshness or volume of rounds.

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 the baseline is 3, but the description goes beyond it by telling the agent where each id comes from (archive-seasons or the event competition block) and that the stage_id must correspond to a published draw. That sourcing guidance is real added meaning not present in 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?

The first two sentences name a specific verb and resource ('Flashscore tournament draw by season and stage') and enumerate exactly what comes back: entrants, ordered bracket rounds, slots, linked match IDs, scores and winners. That level of specificity ('ordered bracket rounds, slots') distinguishes it from a generic tournament-info or cuptree tool without needing to name a sibling.

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?

It gives concrete prerequisites: use the season tournament_id and its stage_id from flashscore-tournament-archive-seasons or an event's competition block, and it states the negative outcome (not found) when a stage has no published draw. What it lacks is any comparison to alternatives such as the sofascore cuptree tool, so an agent has the context but no explicit exclusion rule.

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