Skip to main content
Glama
Tennis Analytics MCP

Tennis Analytics MCP

compare_players

Read-onlyIdempotent

Compare 2 to 6 ATP players side by side on career stats and charting styles, with optional age-for-age milestone trajectories for direct performance analysis.

Instructions

Compare 2 to 6 ATP players side by side across career stats, charting styles, and optional age-for-age milestone trajectories.

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": {
      "players": "<players>"
    },
    "name": "compare_players"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNo
playersYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, open-world behavior, so the description only needs to add operational detail. It does add two useful constraints the schema does not enforce: the 2-to-6 player cardinality and that the age trajectory is optional, which is exactly the kind of context annotations cannot convey.

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?

A single front-loaded sentence with no filler: verb, cardinality, resource qualifier, and compared dimensions all in one pass. Nothing is repeated from the name and nothing is wasted.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. For a two-parameter read tool the description is nearly sufficient, with the only real gap being the identifier format expected in `players`.

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 0%, so the description carries the burden. It partially compensates by constraining `players` to 2-6 entries and marking `age` as optional and trajectory-oriented, but it never says whether players are names, IDs, or slugs, nor what unit or range `age` takes.

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 and resource ("Compare ... ATP players") and enumerates the dimensions compared: career stats, charting styles, and age-for-age milestones. That separates it from single-player siblings like get_player_profile or get_charting_profile, though it never names an alternative for the simpler two-player case (get_head_to_head).

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 2-to-6 player bound and the word "optional" clearly imply when the tool fits (multi-player comparison, age trajectory as an add-on), but there is no explicit when-not guidance or pointer to get_head_to_head for a pair or get_player_profile for a single player. Usage is inferable rather than stated.

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