Skip to main content
Glama

SportStatsAPI

Get snooker and darts tournament

get_snooker_darts_tournament
Read-only

A snooker or darts tournament with its whole draw (qualifying first, the final last): round, players, seeds, frames/legs/sets won, best of, three-dart averages where listed; snooker also the century breaks per player.

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": {
      "sport": "<sport>",
      "tournament_id": "<tournament_id>"
    },
    "name": "get_snooker_darts_tournament"
  }
}

Input Schema

NameRequiredDescriptionDefault
sportYessnooker or darts
tournament_idYestournament code (or number) from get_snooker_darts_tournaments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / tournament_id / description
      Previous value: -"tournament id from get_snooker_darts_tournaments"New value: +"tournament code (or number) from get_snooker_darts_tournaments"
    • changedInput schema / properties / tournament_id / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
  2. Added

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value by describing the returned shape (draw ordered qualifying-first, per-player stats, conditional century breaks for snooker), but says nothing about behavior on missing tournaments, empty draws, or the odd idempotentHint=false.

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?

A single dense sentence with no filler, and the payload enumeration is front-loaded after the resource identification. It is a sentence fragment rather than a stated action, but nothing is wasteful.

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?

With no output schema, the description carries the burden of explaining return values and does so thoroughly for both sports, including the sport-conditional century-break field. Only edge-case behavior (invalid id, tournament not yet started) is unaddressed.

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 coverage is 100% and the schema already explains both parameters, including that tournament_id comes from get_snooker_darts_tournaments and that sport is snooker or darts. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description specifies the resource (a single snooker or darts tournament) and enumerates its payload in detail — full draw, rounds, players, seeds, frames/legs/sets, three-dart averages, century breaks. This distinguishes it clearly from a list tool, though the differentiating verb (fetch one vs. list many) is only implied, not stated.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no mention of the sibling get_snooker_darts_tournaments as the way to discover tournament_ids (that link lives only in the schema), and no note on error behavior if a bad id or sport is supplied. Usage is inferable from the resource name alone, which is a weak baseline.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources