Skip to main content
Glama
Sign In
sportsdata-mcp

sportsdata-mcp

by DanielTomaro13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

wta_tournament_players

Read-onlyIdempotent

Get the entry list and draw for a WTA tournament edition by tournament group ID and year, with seeding, entry types, and final results for singles or doubles.

Instructions

The entry list / draw for one tournament edition — {events:[{eventTypeCode, eventPlayers:[{players:[{id, firstName, lastName}], seed, entryType, eliminated, winner, runnerUp}]}]}. One event per discipline (eventTypeCode LS = Ladies Singles, LD = Ladies Doubles). Carries seeding, entry type, and final results (winner/runnerUp/eliminated). E.g. AO 2025 singles = 128 entrants.

Returns: {events:[{description, eventTypeCode, eventPlayers:[{players:[{id, firstName, lastName, countryCode}], seed, entryType, eliminated, winner, runnerUp}]}]}

Example: Australian Open 2025 entry list + seeds {"groupId": 901, "year": 2025}

Auth: none needed.

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": {
      "groupId": "<groupId>",
      "year": "<year>"
    },
    "name": "wta_tournament_players"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesEdition year (e.g. 2025). Required — part of the URL path.
groupIdYestournamentGroup id (e.g. 901 = Australian Open) — from wta_tournaments. Required — part of the URL path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.24.0
    • addedInput schema / properties / groupId / description
      Added value: +"tournamentGroup id (e.g. 901 = Australian Open) — from wta_tournaments. Required — part of the URL path."
    • addedInput schema / properties / year / description
      Added value: +"Edition year (e.g. 2025). Required — part of the URL path."
  2. Addedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering safety and idempotency. The description adds useful behavioral context beyond annotations: 'Auth: none needed', the per-discipline event structure, and that final results (winner/runnerUp/eliminated) are included. It also clarifies that one event per discipline exists (LS, LD). No contradiction with annotations.

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 description is relatively concise but has some redundancy: the return structure is presented twice (once in the opening and again under 'Returns:'). It efficiently includes event type code definitions, an example, and auth note. The structure is front-loaded with the core purpose, and no unnecessary fluff is present.

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

Completeness5/5

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

For a simple read-only tool with two well-documented parameters and no output schema, the description is complete. It provides the full JSON return shape, explains event types, gives a concrete example call, and notes auth requirements. This is sufficient for an agent to select and invoke the tool correctly in most contexts.

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%, with both groupId and year already clearly documented including their roles and sources. The tool description adds an example call and reiterates that parameters are required part of the URL path, but it does not provide substantially new semantics beyond what the schema already offers. Baseline 3 is appropriate.

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 description clearly identifies the tool's purpose as retrieving 'the entry list / draw for one tournament edition' and provides a detailed return structure including players, seeds, entry types, and final results. It distinguishes itself from sibling tools like wta_tournament_matches by focusing on the player entry list rather than match outcomes, aided by the explicit example of Australian Open 2025.

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 gives a clear context of what the tool does and includes an example request, implying when to use it (when needing tournament entry lists/seeds). However, it does not explicitly mention alternatives or when not to use this tool, so the usage guidance relies on inference rather than explicit direction.

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