Skip to main content
Glama
Tennis Analytics MCP

Tennis Analytics MCP

get_match_charting_stats

Read-onlyIdempotent

Retrieve point-by-point charted tennis match breakdowns—including aces, winners, unforced errors, rally-length distribution, and TML links—for specified players or tournaments.

Instructions

Inspect point-by-point charted match breakdowns (aces, winners, unforced errors, rally length distribution, TML link) from 7,663 MCP matches.

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>"
    },
    "name": "get_match_charting_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
player1Yes
player2No
tournamentNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/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 fully covered by structured data. The description adds that coverage is scoped to the corpus of 7,663 MCP matches, which usefully signals data boundaries, but it says nothing about whether a player without charted matches returns empty results or an error, nor about pagination via the limit parameter.

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?

It is a single front-loaded sentence naming the resource first and the returned fields second, with no filler. The only inefficiency is that the enumerated field list crowds out guidance that would be more valuable given the undocumented parameters.

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 described, and the annotations carry the safety profile. However, with 0% schema description coverage on four parameters including a required player identifier and an optional opponent, the description leaves the agent guessing about filtering semantics for a moderately complex 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 description coverage is 0%, so the schema gives only names and types: player1, player2, tournament, limit. The description does not explain that player1 is required while player2 is an optional opponent filter, nor what tournament expects (name, level, or year), nor what limit bounds. With zero coverage, the description needed to compensate and does not.

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-and-resource pair ("Inspect point-by-point charted match breakdowns") and enumerates the returned dimensions (aces, winners, unforced errors, rally length distribution, TML link), so an agent knows exactly what data this yields. It is less distinct from siblings like get_player_profile or get_head_to_head because it never says explicitly how it differs from them.

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 implied by the phrase "charted match breakdowns" – an agent can infer this is for shot-level charting data rather than aggregate stats – but there is no explicit when-to-use statement, no exclusions, and no named alternative such as compare_players or get_head_to_head. The agent must infer selection criteria from the sibling names alone.

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