Skip to main content
Glama
livetennisapi

livetennisapi-mcp

Charting: player career profile

get_charting_player
Read-onlyIdempotent

Fetch a player's career shot-level profile: serve placement, return depth, net play, clutch-point serving, winners/errors, rally length. Ambiguous names return candidates.

Instructions

Career shot-level profile from the Match Charting Project: serve placement (deuce/ad × wide/body/T), return depth and outcomes, net play, clutch break/game/set-point serving, winners and errors by wing, rally-length tendencies — summed over the player's charted matches. COVERAGE IS CURATED (11,646 charted matches back to the 1960s, concentrated on the majors), not full-slate. An ambiguous name returns the candidates to choose from. Requires the ULTRA plan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesPlayer name fragment, min 3 chars — must resolve to one charted person.
genderNoDisambiguates a name charted on both tours.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesTrue when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures.
playerNoThe resolved charted player.
messageYesHuman-readable summary. Identical to the text content, so either half can be used alone.
coverageNoA reminder that charting coverage is curated, not full-slate.
familiesNoPer-family summed numeric columns — raw sums over the player's charted Total rows.
matches_chartedNoThe sample every summed field covers.
Behavior4/5

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

Annotations already declare read-only/idempotent; the description adds coverage scope, ambiguous-name resolution behavior, and plan restrictions. It does not contradict annotations.

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?

The description is a single dense paragraph that front-loads the main purpose, lists specific data points, and follows with coverage and plan caveats. No filler or repetition.

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

Completeness5/5

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

The description covers what it returns, its data coverage, ambiguity handling, and access restrictions. With an output schema present, this is sufficient for an agent to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema already gives both parameters full descriptions. The description adds that ambiguous names return candidates, enhancing understanding of the name parameter; gender's role is inferred from the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool as returning a 'Career shot-level profile from the Match Charting Project' and enumerates specific stat categories. This specific resource and data type distinguish it from sibling tools like get_player or get_archive_career.

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

Usage Guidelines4/5

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

The description provides context about when this tool is appropriate: when needing shot-level charted career stats. It warns about curated coverage and the ULTRA plan requirement, which implies boundaries, but it does not explicitly name alternative tools or state when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/livetennisapi/livetennisapi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server