Skip to main content
Glama
DanielTomaro13

sportsdata-mcp

wta_rankings

Read-onlyIdempotent

Fetch WTA singles or doubles rankings with player details, points, and movement. Specify type and metric to get an array of ranked players.

Instructions

The WTA rankings — each row is {player:{id, fullName, countryCode, dateOfBirth}, ranking, points, tournamentsPlayed, movement, rankedAt}. Returns a bare ARRAY (not the {pageInfo,content} envelope). REQUIRES type + metric, which must agree: rankSingles+singles or rankDoubles+doubles. Page with page/pageSize (e.g. pageSize=100 for the top 100).

Returns: array of {player:{id, firstName, lastName, fullName, countryCode, dateOfBirth}, ranking, points, tournamentsPlayed, movement, rankedAt}

Example: Top 100 WTA singles rankings {"type": "rankSingles", "metric": "singles", "pageSize": 100}

Auth: none needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo0-based page index.
typeYesRanking type — rankSingles or rankDoubles. Must match `metric`.
metricYesRanking metric — singles or doubles. Must match `type` (rankSingles↔singles, rankDoubles↔doubles).
pageSizeNoRows per page (e.g. 100 = top 100).
Behavior4/5

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

Annotations already declare readOnly, openWorld, and idempotent hints. The description adds useful behavioral details about the response being a bare array and that no authentication is needed. It does not contradict any 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 well-structured with purpose, usage, example, and auth. However, the return row structure is repeated (once in the first sentence and again in the 'Returns:' line), adding slight redundancy.

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 read-only list tool with 4 parameters and no output schema, the description covers the return format, required parameter agreement, pagination, example, and auth. It is sufficiently complete for an agent to invoke correctly.

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 parameters are well-documented. The description adds value by explicitly stating the required type/metric agreement and providing a sample JSON request for the top 100 singles, reinforcing the schema's enum constraints.

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 this tool as returning WTA rankings with a specific row structure. It distinguishes itself from sibling tools like wta_players by focusing on ranking data and explicitly noting the return format (bare array vs envelope). The purpose is unambiguous.

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?

The description provides clear context on how to use the tool: it requires type and metric that must agree, and it gives a concrete example for fetching the top 100 singles. However, it does not explicitly state when to use this versus alternative ranking tools or exclusions.

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