livetennisapi-mcp

Player profile

get_player

Read-onlyIdempotent

Retrieve a tennis player's complete profile, including current ranking, country, handedness, date of birth, and cached statistics. Useful for enriching match data or scouting player details.

Instructions

One player's profile: ranking, country, handedness, date of birth and cached stats. Works on the FREE plan (no card needed).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`player_id`	Yes	Player id, as returned by search_players.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures.
`player`	No	The player.
`message`	Yes	Human-readable summary. Identical to the text content, so either half can be used alone.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.3.0Aug 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already mark the operation read-only, idempotent, and non-destructive. The description adds value beyond that by disclosing that stats are cached and that no payment card is needed on the FREE plan, which gives the agent useful behavioral and access context.

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

Conciseness5/5

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

The description is two concise sentences with no filler. The core purpose is front-loaded, and the additional FREE plan note is relevant and quickly actionable.

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, single-parameter read-only tool with an output schema and rich annotations, the description is sufficient. It explains the profile contents, notes cached data, and clarifies plan availability, leaving no critical gap for an agent to call it correctly.

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 player_id documented as returned by search_players. The tool description does not add extra parameter detail, so baseline 3 is appropriate since the schema carries the burden.

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 one player's profile and lists specific fields (ranking, country, handedness, date of birth, cached stats). This distinguishes it from siblings like get_player_rankings or search_players, which serve different purposes.

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 implies the tool is for fetching a single player's profile and notes it works on the FREE plan, but it does not explicitly state when to use this over alternatives like search_players or get_player_rankings. The schema adds that player_id comes from search_players, providing some routing context.

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