Padel Analyst

show-pair-stats

Read-onlyIdempotent

Get statistics for a pair of players by providing their player IDs. Returns matches played and won, win percentage, sets and games won/lost, titles, finals, semifinals and best round. To get the player IDs, 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_1_id": "<player_1_id>",
      "player_2_id": "<player_2_id>"
    },
    "name": "show-pair-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).
`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).
`player_1_id`	Yes	The ID of the first player in the pair.
`player_2_id`	Yes	The ID of the second player in the pair.

Schema Changelog

Changes observed during successful MCP inspections.

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds useful behavior beyond that: the exact metric set returned and the ID-acquisition path via search-players. It doesn't mention behavior for unknown IDs or empty result sets, which keeps it from a 5.

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, both earning their place: the first defines purpose and return payload, the second handles the prerequisite. The return-field list is front-loaded rather than buried.

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 no output schema, the description usefully enumerates the returned metrics so the agent knows what to expect. Combined with a 100%-covered input schema and rich annotations, it is nearly complete; only edge-case behavior for invalid or unmatched IDs is unaddressed.

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 all six parameters (level, round, after_date, before_date, and the two IDs) are already fully documented in the schema. The description only restates that IDs are supplied as input, adding no syntax or semantic detail beyond the structured fields; baseline 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?

States a specific verb and resource ('Get statistics for a pair of players') and enumerates the returned metrics, so the agent knows exactly what it produces. It does not explicitly contrast itself with the sibling show-player-stats, leaving that distinction to be inferred from 'pair'.

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 prerequisite: use the 'search-players' tool to obtain the player IDs needed as inputs. It doesn't state when to prefer this over show-player-stats or the match-list siblings, but the usage context is otherwise unambiguous.

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?