Skip to main content
Glama
Tennis Analytics MCP

Tennis Analytics MCP

get_head_to_head

Read-onlyIdempotent

Retrieve overall and surface-by-surface head-to-head records plus chronological ATP match results for two players, with optional match limits and match inclusion controls.

Instructions

Get overall and surface-by-surface head-to-head record plus chronological match results between two ATP players.

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": {
      "player1": "<player1>",
      "player2": "<player2>"
    },
    "name": "get_head_to_head"
  }
}

Input Schema

NameRequiredDescriptionDefault
player1Yes
player2Yes
match_limitNo
include_matchesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and idempotency profile is covered. The description adds genuinely useful behavioral context beyond that: the response is broken down by surface and the match list is chronological, which tells the agent what shape of data to expect. It says nothing about how many matches are returned by default or what happens when include_matches is disabled, so the behavioral picture is incomplete.

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 well-formed sentence with no filler, front-loading the primary output (the head-to-head record) before the secondary payload (match results). It is efficient, though the trailing "plus chronological match results" clause is tacked on rather than integrated into a clearly structured statement.

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 the description is not obliged to explain return values, and the annotations cover the safety profile. The remaining gap is parameter coverage: with 0% schema description coverage, the description should explain match_limit and include_matches, but does not. It is adequate for the tool's core purpose but leaves a real hole for two of four parameters.

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%, so all four parameters depend on the description for meaning. It does clarify that player1/player2 are ATP players (implying player names rather than IDs) and that match results are returned, loosely gesturing at include_matches. However, match_limit and include_matches are never named, and the default of 15 matches and the boolean toggle's effect are left entirely undocumented.

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 states a specific verb and resource ("Get head-to-head record ... between two ATP players") and adds scope detail: overall and surface-by-surface splits plus chronological match results. That is far more informative than the bare tool name. It stops short of distinguishing itself from the sibling compare_players, which could plausibly be read as overlapping, so it earns a 4 rather than 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 Guidelines2/5

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

There is no when-to-use guidance, no stated preconditions, and no mention of alternatives such as compare_players or search_matches. The agent must infer entirely from the phrase "head-to-head" when this tool is the right choice. Nothing in the text says when NOT to reach for it.

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