Skip to main content
Glama

SportStatsAPI

Get snooker and darts player

get_snooker_darts_player
Read-only

A snooker or darts player (player_id): country, world ranking, birth date (Wikidata), titles and finals in the stored seasons, latest matches; or find players by name.

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>"
    },
    "name": "get_snooker_darts_player"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNopart of a player's name, to find the id
sportYessnooker or darts
player_idNoplayer code (or number) from a draw or ranking

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.5/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 safety is covered. The description adds a bit beyond that by disclosing data provenance ('Wikidata') and scope ('titles and finals in the stored seasons', 'latest matches'), which hints at coverage limits. It says nothing about how a name search behaves (single match vs list), so behavior under partial matches is unknown.

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?

It is a single compact sentence, front-loaded with the resource and followed by the returned fields, then the alternative name lookup. The semicolon chain of field names is dense but every element is informative; nothing is redundant with the title.

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?

There is no output schema, so the description carries the burden of describing return values, and it does list the main fields (country, ranking, birth date, titles/finals, latest matches). The main residual gap is what a name lookup returns and whether results are paginated, which matters for a tool with two distinct modes.

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%, so each parameter already carries its own description; the baseline is 3. The description reinforces that player_id is the primary key for the field list and that name is a partial-name lookup for finding the id, but it adds no format detail or precedence rules beyond the schema.

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 names the resource (a snooker or darts player) and enumerates the fields it returns, plus a secondary lookup-by-name mode. The sport qualifier implicitly separates it from get_golf_player / get_boxing_fighter, but it never states how it differs from the generic get_player sibling.

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 trailing clause 'or find players by name' implies an alternative usage mode (search rather than fetch by id), which gives an agent some routing signal. There is no explicit when-to-use advice, no statement of which mode to pick when both name and player_id could be supplied, and no mention of alternatives.

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