Padel Analyst

search-matches

Read-onlyIdempotent

Search matches by ID, date, round, category, draw or tournament level. Returns each match with its tournament, round, both teams with their players and seeds, scheduled time, court, status, score, winner and duration. To list all matches of a tournament, use the "list-tournament-matches" tool.

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

Name	Required	Description	Default
`id`	No	Match ID(s) to retrieve, comma-separated (e.g. `1,2,3`). Only returns matches of the default `draw=main` unless `draw=all` is passed.
`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
`category`	No	Category of the match. Either `men` or `women`.
`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.
`after_date`	No	Filter matches played after this date (YYYY-MM-DD).
`before_date`	No	Filter matches played before this date (YYYY-MM-DD).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 10, 2026

removedInput schema / properties / court

Removed value: -{
-  "description": "Filter matches by court name (partial match).",
-  "type": "string"
-}

addedInput schema / properties / level

Added value: +{
+  "description": "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.",
+  "type": "string"
+}

changedInput schema / properties / sort_by / enum

Previous value: -[
-  "watchability",
-  "round",
-  "played_at"
-]New value: +[
+  "watchability",
+  "played_at"
+]

First observedOct 30, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, non-destructive, closed world), so the description's job is to add context — and it does by enumerating the returned fields (tournament, round, teams with players and seeds, time, court, status, score, winner, duration) in the absence of an output schema. It adds no auth, rate-limit, or empty-result behavior, so it stops short of full disclosure.

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?

Three sentences, front-loaded with the capability, then the payload, then the routing hint. Nothing is redundant given the schema already carries parameter detail.

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?

For an 11-parameter read tool with no output schema, the description supplies both the searchable facets and the shape of the returned match object, plus the alternative for tournament listing. That is everything an agent needs to select and invoke it correctly, with remaining detail delegated to a fully documented schema.

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%, with enums and per-parameter prose already explaining draw defaults, round encoding, level taxonomies, and pagination. The description only restates the filter list and adds no syntax, precedence, or combination semantics beyond the schema, so the baseline 3 applies.

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?

States a specific verb+resource ("Search matches") and enumerates the filterable dimensions (ID, date, round, category, draw, tournament level), then names the sibling it is not for tournament-wide listing. An agent can separate it from list-tournament-matches without opening either schema.

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?

Explicitly routes tournament-wide listing to "list-tournament-matches", which is a concrete when-to-use-other rule. It does not address the other plausible alternatives in the sibling set (list-player-matches, list-pair-matches, search-headtohead), so the guidance is clear but not exhaustive.

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?