Skip to main content
Glama
DanielTomaro13

sportsdata-mcp

wta_players

Retrieve WTA player profiles by name or browse all players. Get player IDs, names, country codes, and birth dates for use in further queries.

Instructions

The WTA player catalogue — {pageInfo, content:[{id, firstName, lastName, fullName, countryCode, dateOfBirth}]}. Search by name (e.g. 'Swiatek' → Iga Swiatek) or page through all. The player id feeds wta_player / wta_player_matches.

Returns: {pageInfo:{numPages, totalElements}, content:[{id, firstName, lastName, fullName, countryCode, dateOfBirth, metadata}]}

Example: Find Iga Swiatek

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
pageNo
pageSizeNo
Behavior4/5

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

Without annotations, the description explains the return structure, example usage, and relationship to other tools. It does not discuss side effects, rate limits, or authentication, but it provides sufficient behavioral context for a read operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is reasonably concise but contains redundancy in the return structure (stated twice) and could be more streamlined. It is front-loaded with the core purpose but includes repeated information.

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?

The description explains the return format, provides an example, and indicates how the tool fits into a workflow. Given no output schema, it is fairly complete. Missing details like maximum page size or error handling, but adequate for a simple list tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, so the description must explain parameters. It only explains the 'name' parameter and hints at pagination, but does not explicitly document the 'page' and 'pageSize' parameters, their defaults, or their behavior.

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 'WTA player catalogue' and explains it is used to search or list players. It distinguishes from siblings like 'wta_player' and 'wta_player_matches' by mentioning the player id feeds these tools.

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 explicit guidance: search by name or page through all. It also explains the downstream use of the player id. However, it does not explicitly state when not to use the tool or compare with alternatives.

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