Skip to main content
Glama
Tennis Analytics MCP

Tennis Analytics MCP

search_players

Read-onlyIdempotent

Find Open Era ATP players by name fragment, country code, or Grand Slam champion status to identify player records before running match or career analytics.

Instructions

Search 7,622 Open Era ATP players by name fragment, 3-letter country code (e.g. ESP, ITA, IND), or Grand Slam status.

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": "search_players"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
countryNo
min_matchesNo
grand_slam_champions_onlyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds useful dataset context (Open Era ATP, 7,622 players) but says nothing about result ordering, default result count, or how min_matches filters the pool — behavior an agent would want before invoking.

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 that packs the scope, the three usable search keys, and format examples with no filler or repetition. Nothing in it could be removed without losing information.

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. However, with five parameters at 0% schema coverage and no annotations gap to lean on for input semantics, the definition is missing limit behavior, min_matches meaning, and match/ordering semantics — enough that an agent must guess on part of the call surface.

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 and partially discharges it: it clarifies that query is a name fragment, that country takes a 3-letter code with concrete examples (ESP, ITA, IND), and that grand_slam_champions_only is a status filter. It never mentions the limit or min_matches parameters, leaving two of five undocumented anywhere.

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 ('Search') plus the exact resource and scope: '7,622 Open Era ATP players.' An agent immediately knows this is a player lookup, not a match or stats query, which separates it from siblings like search_matches and get_player_profile. It stops short of naming a sibling it must not be confused with, so it is clear but not maximally differentiated.

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?

Usage is only implied by the listed search keys (name fragment, country, Grand Slam status); there is no explicit 'use this when' statement, no exclusion telling the agent when to prefer get_player_profile or compare_players instead, and no note on what to do with zero results. The agent can infer the right context but receives no routing guidance.

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