Skip to main content
Glama
Tennis Analytics MCP

Tennis Analytics MCP

get_charting_profile

Read-onlyIdempotent

Retrieve detailed shot and rally statistics for a tennis player, including serve win rates, return percentages, rally length, and error rates, to analyze performance by surface.

Instructions

Get Jeff Sackmann Match Charting Project shot/rally profiles (1st/2nd serve win%, return%, rally length, UF error rate, Serve+1, BP save delta) across 475 players.

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_charting_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sort_byNomcp_match_count
surfaceNo
min_matchesNo
player_nameNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered externally. The description adds genuinely useful scope ('across 475 players') and tells the agent which metric domains are present in the response. It says nothing about how filters interact, what happens with an unknown player_name, or pagination/limit behavior, so the added context is real but thin.

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 dense sentence that front-loads the source and resource, then the metric list, then the population size. Nothing is wasted, though the parenthetical metric inventory is long and still leaves the parameter surface unaddressed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The presence of an output schema means return values need not be explained, and the annotations cover safety. But for a five-parameter, zero-coverage schema with non-obvious defaults (limit=15, sort_by='mcp_match_count', min_matches=10), omitting all parameter guidance leaves the agent guessing at filtering and ordering behavior.

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% across five parameters (limit, sort_by, surface, min_matches, player_name) with no enum constraints, so the schema carries essentially no semantics and the description must compensate. The description never mentions any parameter — not that results can be narrowed by surface or player_name, nor what sort_by accepts or what min_matches defaults to. The metric list hints at what is returned but adds no invocation guidance.

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 uses a specific verb ('Get') plus a named resource ('Jeff Sackmann Match Charting Project shot/rally profiles') and enumerates the metric families returned (serve win%, return%, rally length, UF error rate, Serve+1, BP save delta). It also states the data scope ('across 475 players'), which lets an agent separate it from match-level lookup. It stops short of naming a sibling like get_match_charting_stats, so the differentiation is implied rather than explicit.

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 or when-not-to-use guidance and no mention of alternatives such as get_match_charting_stats or get_player_profile. An agent can infer from the metric list that this is a player-level charting profile, but nothing states the conditions that select this tool over its siblings.

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