Skip to main content
Glama
Tennis Analytics MCP

Tennis Analytics MCP

get_young_guns_race

Read-onlyIdempotent

Compare ATP next-wave talents like Fonseca, Mensik, Tien, and Jodar against Alcaraz and Sinner age benchmarks to assess their career trajectories.

Instructions

Track ATP next-wave talents (Joao Fonseca, Jakub Mensik, Learner Tien, Rafael Jodar) against Alcaraz and Sinner age benchmarks.

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_young_guns_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

C2.8/5.0
Behavior2/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 description owes context beyond that. It supplies none: no indication of what happens when both filters are null (all players?), how the age benchmark is computed, or what freshness/coverage the data has.

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 with no filler; the player examples help ground the scope. Slightly wasteful in that the enumerated names are the only concrete content, but nothing is padded.

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 small (2 optional params). Still, with zero parameter documentation and no routing guidance among similar siblings, an agent cannot fully predict what a call with given arguments will produce.

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 two parameters (age, player), and the description never mentions either. The player names in the text hint that filtering by player is possible, but nothing explains what 'age' means (player age at comparison? benchmark age?) or how the two interact.

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 names a concrete subject (ATP 'next-wave' players such as Fonseca, Mensik, Tien, Jodar) and a concrete comparison (Alcaraz and Sinner age benchmarks), so an agent can tell this is a young-player-vs-benchmark tracker. It does not, however, distinguish itself from the obvious sibling get_greatness_race, leaving overlap ambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use, when-not-to-use, or alternative-tool guidance at all. The closest sibling, get_greatness_race, is never mentioned, so an agent has no stated basis for choosing between the two.

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