Skip to main content
Glama
DanielTomaro13

sportsdata-mcp

wta_tournaments

Retrieve the WTA tournament calendar with details on dates, surface, location, prize money, and winners. Paginate through results across all years.

Instructions

The WTA tournament calendar — {pageInfo, content:[{tournamentGroup:{id, name, level}, year, title, startDate, endDate, surface, inOutdoor, city, country, singlesDrawSize, doublesDrawSize, prizeMoney, level, status, winners}]}. Take a row's tournamentGroup.id + year for wta_tournament / wta_tournament_matches. Page through with page/pageSize (the list spans all years).

Returns: {pageInfo:{numPages, totalElements}, content:[{tournamentGroup:{id, name, level}, year, title, startDate, endDate, surface, inOutdoor, city, country, singlesDrawSize, doublesDrawSize, prizeMoney, prizeMoneyCurrency, level, status, winners, liveScoringId}]}

Example: Browse tournaments

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
pageSizeNo
Behavior4/5

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

No annotations are provided, so the description bears the full burden. It implies a read-only operation (browsing a calendar) and details the output structure. However, it does not explicitly state that the tool is non-destructive or idempotent, nor does it mention any potential side effects, which is a minor gap.

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 moderately concise, front-loading the purpose and pagination guidance. It includes a detailed output structure that could be offloaded to an output schema if one existed. While not overly verbose, it could be slightly more compact without losing necessary detail.

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?

Despite lacking annotations and an output schema, the description covers all necessary aspects: what the tool returns (with structure), how to paginate, and how to use results with related tools. It feels complete for a read-only list endpoint with no filtering options.

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 description coverage is 0%, meaning the input schema properties are not described in detail. However, the description includes 'Page through with page/pageSize', which adds meaning to the two integer parameters. Given the simplicity of pagination parameters, this is sufficient compensation, though more detail (e.g., bounds, behavior) would improve clarity.

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 states the tool returns the WTA tournament calendar, listing tournaments with pagination. It explicitly contrasts with wta_tournament and wta_tournament_matches for drilling into specific tournaments, making it distinct from its siblings.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool: to browse the full list of tournaments across all years, and then use the tournamentGroup.id and year from a row to call wta_tournament or wta_tournament_matches for details. It also explains pagination with page/pageSize.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DanielTomaro13/sportsdata-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server