Padel Analyst

search-tournaments

Read-onlyIdempotent

Search tournaments by name and other filters to get tournament details: location, venue, country, level, format (pairs or teams), status, court type, prize money, dates and poster image.

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

Input Schema

Name	Required	Description
`id`	No	Tournament ID(s) to retrieve, comma-separated (e.g. `1,2,3`).
`name`	No	Name of the tournament to search for.
`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.
`format`	No	Filter by how the tournament is contested: `pairs` for regular draws or `teams` for team competitions such as the FIP World Cup.
`country`	No	2-letter country code of the tournament location (e.g. `ES`, `FR`).
`sort_by`	No	Field to sort the tournaments by (name, location, country, level, start_date, end_date).
`location`	No	City or location where the tournament is held.
`order_by`	No	Order of the sorting, either `asc` or `desc`.
`per_page`	No	Number of results per page (1-50). Use a small value when you only need the top results, or 50 to minimize pages when you need the complete list.
`after_date`	No	Filter tournaments still running on or after this date (YYYY-MM-DD).
`court_type`	No	Filter by court type. Either `indoor`, `outdoor` or `covered`.
`before_date`	No	Filter tournaments already started on or before this date (YYYY-MM-DD).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026

changedInput schema / properties / location / description

Previous value: -"Name of the city/location to held the tournament."New value: +"City or location where the tournament is held."

changedInput schema / properties / per_page / description

Previous value: -"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."New value: +"Number of results per page (1-50). Use a small value when you only need the top results, or 50 to minimize pages when you need the complete list."

First observedOct 30, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is fully covered. The description adds the returned field list, which is genuinely useful given there is no output schema, but says nothing about pagination behavior, result limits, or empty-result handling.

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 front-loaded sentence with no filler; the purpose comes first and the field list follows. The trailing enumeration is long but each item is informative rather than redundant.

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 13-parameter, all-optional search tool with full schema coverage, the description adequately conveys scope and return contents, partially compensating for the missing output schema. Pagination and result-count expectations are left to the schema, which is a minor remaining gap.

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 includes enums, examples, and pagination instructions, so the schema carries parameter meaning. The description only gestures at 'name and other filters' and adds no syntax, defaults, or filter-combination semantics 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?

States a specific verb (search) and resource (tournaments) and enumerates the detail fields returned, so the agent knows exactly what it gets back. It does not explicitly distinguish itself from siblings like list-tournament-matches, which is the only thing keeping it from a 5.

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

Usage Guidelines3/5

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

Usage is only implied by the filter set ('search by name and other filters'); there is no statement of when to prefer this over list-tournament-matches or search-seasons, nor any exclusions. An agent can infer the use case but must reason about alternatives itself.

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?