Skip to main content
Glama
Tennis Analytics MCP

Tennis Analytics MCP

search_matches

Read-onlyIdempotent

Search 200,105 ATP matches by player, opponent, tournament, surface, round, year range, Grand Slam filter, or comeback score to find specific tennis records.

Instructions

Search 200,105 ATP matches by player, opponent, tournament, surface (Hard/Clay/Grass/Carpet), round, year range, Grand Slam filter, or comeback score.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
playerNo
sort_byNorecent
surfaceNo
year_toNo
opponentNo
year_fromNo
round_nameNo
tournamentNo
grand_slam_onlyNo
min_comeback_scoreNo

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=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered and the bar is lower. The description adds useful context the annotations do not: corpus size (200,105 matches) and the full surface vocabulary. It is silent on result ordering, pagination/limit behavior, and matching semantics (exact vs partial player names).

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 with the resource and corpus size front-loaded and the filter set following; no filler or repetition. It is arguably over-packed with an enumeration that could be grouped (time filters, entity filters), but nothing is wasted.

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-value explanation is not required, and the read-only annotations relieve behavioral burden. Still, for an 11-parameter search with zero schema documentation, leaving limit and sort_by undescribed and result-set semantics unstated is a real gap for correct invocation.

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% across 11 parameters with no enums, so the description carries real weight and does deliver meaning for about eight of them: player, opponent, tournament, surface (with the Hard/Clay/Grass/Carpet vocabulary that the schema lacks), round, year range, Grand Slam flag, and comeback score. However, it omits 'limit' and 'sort_by', both of which materially change results, and it never clarifies matching behavior for name-based fields.

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?

States a specific verb ('Search') and resource ('ATP matches', with corpus size 200,105) and enumerates the filterable dimensions, so an agent knows exactly what this tool retrieves. It is clearly distinct from the player-aggregate siblings (search_players, get_head_to_head) by virtue of operating on match records, though the description never names or contrasts those alternatives explicitly.

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 / when-not-to-use guidance and no alternative tool named. The only usage signal is the list of filter fields, which is essentially a restatement of the input schema rather than routing advice; an agent cannot tell from this text whether head-to-head or charting tools should be preferred for overlap cases.

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