Skip to main content
Glama
Tennis Analytics MCP

Tennis Analytics MCP

get_greatness_race

Read-onlyIdempotent

Compare Big 3, Alcaraz, Sinner, Borg, Sampras, McEnroe, Lendl, and Agassi by titles, Slams, and Masters at any age.

Instructions

Compare Big 3, Alcaraz, Sinner, Borg, Sampras, McEnroe, Lendl, and Agassi on titles, Slams, and Masters at any age.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_greatness_race"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNo
playerNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this as read-only, idempotent, open-world, and non-destructive, so the safety profile is covered. The description adds domain scope by saying it compares historical greats across ages, but it does not clarify null/default behavior, data coverage, or how the age comparison works.

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 a single front-loaded sentence with no filler. It efficiently names the players, metrics, and age scope.

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?

The output schema and annotations reduce what the description must cover, and the description establishes the comparison domain. Still, with 0% schema description coverage, it leaves key parameter semantics and sibling selection ambiguous, so it is only minimally complete for an optional two-parameter query 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?

Schema coverage is 0%, so the description must compensate for both parameters. It hints that age is relevant via 'at any age' and lists player names, but it never explains whether the player parameter accepts one of those names, 'Big 3', or any player, nor what the age value means or what happens when either parameter is omitted.

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 clearly states a specific comparison action: it compares named all-time great players on titles, Slams, and Masters at any age. The player set and metrics make the tool's domain clear. It does not explicitly distinguish itself from siblings such as compare_players or get_young_guns_race, so it falls short of a 5.

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 when this tool is useful: comparing this particular group of legends across ages. However, it gives no explicit when-to-use versus alternatives or when-not-to-use guidance, and it does not mention siblings like compare_players or get_young_guns_race.

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