Padel Analyst

search-players

Read-onlyIdempotent

Search players by ID, name, nationality, category, birthplace or side. Returns the player ID, name, category, nationality, current ranking and points, Padel API Elo, height, side (drive/backhand), hand, birthplace, birthdate and age.

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

Input Schema

Name	Required	Description	Default
`id`	No	Player ID(s) to retrieve, comma-separated (e.g. `1,2,3`).
`name`	No	Name or surname of the player (or players) to search for. Matches any part of the full name, ignoring case and accents, so prefer the surname over a first name or nickname. To search for multiple players, separate names or surnames with commas.
`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.
`side`	No	Side of the player, either `drive` or `backhand`.
`sort_by`	No	Name of the parameter to sort the players by.	name
`category`	No	Category of the player. Either `men` or `women`.
`order_by`	No	Order of the sorting, either `asc` or `desc`.	asc
`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.
`birthplace`	No	Name of the birthplace of the player.
`nationality`	No	2-letter country code of the player (e.g. `ES`, `AR`). If the country is not clearly specified, omit this parameter.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026

changedInput schema / properties / name / description

Previous value: -"Name or surname of the player (or players) to search for. To search for multiple players, separate names or surnames with commas."New value: +"Name or surname of the player (or players) to search for. Matches any part of the full name, ignoring case and accents, so prefer the surname over a first name or nickname. To search for multiple players, separate names or surnames with commas."

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.6/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 openWorldHint=false, so the safety profile is covered. The description then adds real value beyond that by enumerating the full return surface (IDs, ranking, points, Elo, physical attributes, age), which is important because there is no output schema; it omits only the pagination behavior, which lives in the 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, zero filler: the first front-loads the searchable dimensions and the second front-loads the return payload. Every clause carries information an agent would otherwise have to infer from the schema.

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?

Because there is no output schema, the description must characterize the response, and it does so thoroughly. The remaining gap is behavioral rather than structural: it does not state that results are paginated, that an empty filter returns the full paginated roster, or how results are ordered by default, all of which matter given ten optional parameters.

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%, so the schema already carries the meaning of all ten parameters, including enums, defaults, the per_page range and the comma-separation convention. The description restates the filterable fields but adds no syntax or matching nuance (for example accent-insensitive partial matching) beyond what the schema says, so the baseline of 3 applies.

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 description names a specific verb (search) and resource (players) and enumerates the exact filter dimensions: ID, name, nationality, category, birthplace and side. That is enough for an agent to tell it apart from search-pairs or search-matches, though it never explicitly contrasts itself with show-player-stats, which is the closest sibling for player detail.

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 or when-not-to-use guidance. With siblings like show-player-stats and search-pairs in the same namespace, the agent gets no signal about whether to call this for a lookup versus a detail fetch, and no note that all filters are optional and combinable.

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?