Padel Analyst

show-player-stats

Read-onlyIdempotent

Get career statistics for a player by providing their player ID. Returns matches played and won, win percentage, sets and games won/lost, titles, finals, semifinals and best round. 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": "show-player-stats"
  }
}

Input Schema

Name	Required	Description
`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 stats by match round (1 = Final, 2 = Semifinal, 4 = Quarterfinal, 8 = Round of 16, 16 = Round of 32, 32 = Round of 64).
`player_id`	Yes	The ID of the player to get statistics for.
`after_date`	No	Calculate stats from matches played after this date (YYYY-MM-DD).
`before_date`	No	Calculate stats from matches played before this date (YYYY-MM-DD).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds the result field list and the dependency on search-players for the ID. It says nothing about whether filters change the shape of the response, caching, or empty-result behavior when a player has no matches at a given level/round.

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 tight sentences with zero waste: purpose and output first, then the prerequisite lookup path. Front-loaded and appropriately sized for a read-only stats query.

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?

With annotations covering safety and a 100%-documented input schema, the description supplies what structured fields cannot: the return payload contents and how to obtain the required ID. No output schema exists, but the enumerated metrics effectively serve that role. Minor gap: no mention of what happens with unsupported or mixed filter combinations.

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 a fully enumerated level list and round mapping, so the schema does the heavy lifting. The description only glosses player_id and mentions no semantics for the level, round, after_date or before_date filters. Baseline 3 is appropriate.

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 and resource ("Get career statistics for a player") and immediately enumerates the returned metrics: matches played/won, win percentage, sets and games, titles, finals, semifinals, best round. This distinguishes it clearly from siblings such as show-pair-stats and show-match-stats, which cover different entities.

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?

Gives a clear entry condition ("by providing their player ID") and routes the agent to the prerequisite tool: "To get the player ID, use the search-players tool." That is a genuinely useful workflow hint. It stops short of explicit when-not guidance or naming alternatives for aggregate stats (e.g., show-pair-stats), so it is not a 5.

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?