Cito API

player_matches

Read-only

Tennis player match log: every archived match for one player, newest first, with opponent, tournament, round, surface and score.

When to use:

"Show me Shelton's last 20 matches"; full match history; every match at a given tournament; filtering a player's record by surface.

Prefer over: player_form (a W/L summary with a small window and a streak, not the log); call_api for /tennis/players/{id}/matches.

Do not use when: aggregate totals, titles, or win% → player_stats; identity → player_profile; one match's box score → match_details.

Tennis-only. Limit defaults to 20 (max 50). Rows arrive newest-first. Use surface to narrow to Hard/Clay/Grass; tournamentId pins one event.

Parallel-safe: yes. Upstream cost: 1.

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": {
      "game": "<game>",
      "playerId": "<playerId>"
    },
    "name": "player_matches"
  }
}

Input Schema

Name	Required	Description
`game`	Yes	Game title: lol \| cs2 \| dota2 \| cod \| ufc \| tennis \| valorant. Example: "cs2".
`limit`	No	Match rows (default 20, max 50).
`surface`	No	Filter to one surface: Hard, Clay, or Grass.
`playerId`	Yes	Tennis player id, e.g. "atp_210097".
`tournamentId`	No	Only matches at this tournament edition, e.g. "atp_2026_560".

Output Schema

Name	Required	Description
`ok`	Yes	true if the tool succeeded
`data`	No	Result payload when ok is true; null on error
`meta`	Yes
`error`	No
`partial`	No
`pagination`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 14, 2026

changedInput schema / properties / game / description

Previous value: -"Game title: lol | cs2 | dota2 | cod | ufc | tennis. Example: \"cs2\"."New value: +"Game title: lol | cs2 | dota2 | cod | ufc | tennis | valorant. Example: \"cs2\"."

changedInput schema / properties / game / enum

Previous value: -[
-  "lol",
-  "cs2",
-  "dota2",
-  "cod",
-  "ufc",
-  "tennis"
-]New value: +[
+  "lol",
+  "cs2",
+  "dota2",
+  "cod",
+  "ufc",
+  "tennis",
+  "valorant"
+]

AddedSep 12, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare read-only/non-destructive/open-world; the description adds ordering guarantees (newest-first), a hard cap (max 50), a tennis-only restriction, parallel-safety, and upstream cost of 1 — real operational context not present in the structured fields.

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?

Front-loaded purpose followed by labeled sections; nearly every line earns its place. Minor redundancy in repeating limit default/max and surface values already shown in the schema keeps it just below the top mark.

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?

With an output schema handling return values and annotations covering the safety profile, the description supplies the remaining essentials: scoping (tennis-only), filtering semantics, ordering, caps, and cost. Nothing needed to invoke it correctly is missing.

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 coverage is 100%, so surface values, limit bounds, and playerId/tournamentId examples are already documented. The description restates limit default/max and surface values, adding only mild framing ('tournamentId pins one event'), so it does not substantially exceed the schema baseline.

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?

Opens with a specific verb+resource ('Tennis player match log: every archived match for one player') and states the row shape (opponent, tournament, round, surface, score) and ordering (newest first). An agent can distinguish this from player_form, player_stats, and match_details without opening any schema.

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

Usage Guidelines5/5

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

Explicit when-to-use examples ('Show me Shelton's last 20 matches', full history, per-tournament, per-surface), an explicit 'Prefer over' routing line naming player_form and raw call_api, and an explicit 'Do not use when' block routing totals to player_stats, identity to player_profile, and box scores to match_details.

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

All Cito API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?