Skip to main content
Glama
Tennis Analytics MCP

Tennis Analytics MCP

get_player_profile

Read-onlyIdempotent

Retrieve a tennis player's ATP career stats, surface splits, top-10 win rates, charting profile, and recent matches by name to analyze performance.

Instructions

Get a player's full ATP career stats, surface splits, top-10 win rates, Match Charting Project profile (if charted), and recent matches.

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": {
      "player_name": "<player_name>"
    },
    "name": "get_player_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
player_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuine behavioral context by flagging that charting data appears only 'if charted' and that recent matches are included, but it says nothing about behavior when a player is unmatched, ambiguous, or when a data section is unavailable.

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?

A single front-loaded sentence that opens with the core action and then enumerates the returned data. Every clause maps to actual content; the only mild inefficiency is that the list is dense without grouping or priority.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the tool is structurally simple with one required parameter. However, for a broad aggregate endpoint the definition leaves real gaps: how player names are matched or disambiguated, and what happens when the charting section is absent. It is minimally sufficient but not complete.

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?

Schema description coverage is 0% for the single parameter, so the description must carry the burden and it does not: it says nothing about whether player_name expects a full name, a partial name, a case-sensitive form, or how ambiguous or accented names are resolved. The parameter is largely self-explanatory by name, which keeps this above a 1, but no compensating detail is provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('Get') and resource ('a player's full ATP career stats') and enumerates what the profile contains: surface splits, top-10 win rates, Match Charting Project data, and recent matches. It is clearly a one-stop aggregate profile tool, distinct from narrow siblings like get_charting_profile or get_gsdi_rankings, though it never explicitly contrasts itself with them.

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 enumeration of contents implies when the tool is appropriate (a broad single-player lookup), but there is no explicit 'use this when' guidance and no routing to alternatives such as get_charting_profile for charting-only data or compare_players for two-player questions. Useful implication, but nothing is stated about when not to use it.

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