Padel Analyst

list-player-rankings

Read-onlyIdempotent

Get ranking snapshots for a player by providing their player ID. Each entry includes the ranking type (official/race/elo), position, points and diffs against the previous snapshot. For type elo the points field carries the Elo rating, so the series is the evolution of the rating over time. Without date filters returns the latest entry per type; with date filters returns the weekly historical series in that range. 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": "list-player-rankings"
  }
}

Input Schema

Name	Required	Description
`type`	No	Filter by ranking type. Omit to return all of them.
`player_id`	Yes	The ID of the player to get rankings for.
`after_date`	No	Start date of the historical series (YYYY-MM-DD).
`before_date`	No	End date of the historical series (YYYY-MM-DD).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds real behavioral context beyond them: the shape of each returned entry, the Elo-specific meaning of the points field, and how date filters switch output from a single snapshot to a weekly series. Nothing an agent needs behaviorally is undisclosed.

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?

Four tight sentences, front-loaded with purpose, then return shape, then the mode-switching rule, then the dependency pointer. No filler and nothing repeated from the schema.

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?

There is no output schema, so the description carries the return-value burden itself and does so: it lists the entry fields and explains the elo special case. For a 4-parameter read-only lookup, an agent has everything it needs to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds genuine semantics the schema does not: the `type=elo` case reinterprets `points` as an Elo rating, and the presence/absence of date parameters changes the result mode rather than merely filtering. Only the after/before date interaction (inclusive? weekly boundaries?) is left unstated.

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 ranking snapshots for a player') and immediately enumerates what each entry contains (type, position, points, diffs). An agent knows exactly what comes back. It does not, however, distinguish itself from the sibling 'list-rankings', which an agent could easily confuse with a per-player ranking lookup.

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

Usage Guidelines5/5

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

Explicitly defines the two operating modes: no date filters returns the latest entry per type, with date filters returns the weekly historical series in that range. It also names the prerequisite tool ('use the "search-players" tool' to obtain player_id), removing the main ambiguity an agent would face before calling.

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?