Padel Analyst

list-player-matches

Read-onlyIdempotent

List the matches of a player by providing their player ID. Returns each match with its tournament, round, both teams with their players and seeds, scheduled time, court, status, score, winner and duration. To get the player ID, use the "search-players" tool.

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": {
      "player_id": "<player_id>"
    },
    "name": "list-player-matches"
  }
}

Input Schema

Name	Required	Description	Default
`draw`	No	Draw the matches belong to: `main`, `qualy`, `group` or `placement` (team tournaments only), or `all` for every draw in a single list. Defaults to `main`: the other draws are only returned when explicitly requested.	main
`page`	No	Page number for pagination. Results are paginated: check `meta` (`current_page`, `last_page`, `total`) in the response and request further pages with this parameter until you have all the results you need.
`level`	No	Filter by tournament level(s), comma-separated. Premier Padel: major, p1, p2, finals. FIP tour: fip_platinum, fip_gold, fip_silver, fip_other. World Padel Tour (historical): wpt_master, wpt_1000, wpt_500, wpt_final. Padel Pro Tour (historical): ppt_master, ppt_final, ppt_international, ppt_promotional, ppt_other.
`round`	No	Filter matches by round (1 = Final, 2 = Semifinal, 4 = Quarterfinal, 8 = Round of 16, 16 = Round of 32, 32 = Round of 64, 0 = group stage of team tournaments).
`sort_by`	No	Sort matches by this field.	played_at
`order_by`	No	Order of the sorting, either `asc` or `desc`.	desc
`per_page`	No	Number of results per page (1-50). Use a small value when you only need the top results (e.g. 1 for the most recent match), or 50 to minimize pages when you need the complete list.
`rival_id`	No	Filter matches played against this player ID.
`player_id`	Yes	The ID of the player whose matches to list.
`after_date`	No	Filter matches played after this date (YYYY-MM-DD).
`before_date`	No	Filter matches played before this date (YYYY-MM-DD).
`tournament_id`	No	Filter matches by tournament ID.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026

addedInput schema / properties / rival_id

Added value: +{
+  "description": "Filter matches played against this player ID.",
+  "type": "integer"
+}

First observedOct 30, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds genuine value by enumerating the returned payload (tournament, round, teams with players and seeds, schedule, court, status, score, winner, duration), which is not derivable from the annotations and matters since there is no output schema.

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?

Two sentences: the first states the action and the required argument, the second states the return shape, and a trailing sentence handles the ID lookup dependency. No filler, correctly front-loaded.

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

Completeness4/5

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

For a 12-parameter read tool with no output schema, the description covers the two things an agent most needs — how to obtain player_id and what comes back. Pagination and per-page defaults are only in the schema, but that is acceptable given full schema coverage.

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 100% and every filter (draw, level, round, date bounds, rival_id, sort, pagination) is already documented in-schema. The description adds only the player_id requirement and implies the result set is player-scoped, so it does not meaningfully extend parameter meaning beyond the schema.

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 first sentence states a specific verb and resource — list the matches of a player — plus the required input (player ID). It does not explicitly contrast with the near-identical siblings list-pair-matches or list-tournament-matches, so an agent must infer the boundary from the noun 'player' alone.

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?

It gives a concrete prerequisite workflow, directing the agent to search-players when the player ID is unknown, which is the main when-to-use question here. It stops short of stating exclusions, e.g. when to prefer list-pair-matches or search-matches over this tool.

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

All Padel Analyst 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?