Skip to main content
Glama

Padel Analyst

show-player-form

Read-onlyIdempotent

Get the form of a player by providing their player ID: results against what their Elo rating predicted. Returns expected and actual win rate, the delta between them and matches played over the window (last 180 days by default), the same values by month with their trend (rising, stable or declining), rolling windows of the last 7, 30 and 90 days, the same window one year earlier, the current win or loss streak, and the record in third sets and tiebreaks. 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-form"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNoFilter 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.
roundNoFilter by match round (1 = Final, 2 = Semifinal, 4 = Quarterfinal, 8 = Round of 16, 16 = Round of 32, 32 = Round of 64).
player_idYesThe ID of the player to get the form for.
after_dateNoStart of the window (YYYY-MM-DD). Defaults to 180 days before before_date.
before_dateNoEnd of the window (YYYY-MM-DD). Defaults to today.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real value beyond that by enumerating the computed outputs (expected vs actual win rate, delta, monthly trend classification, 7/30/90-day rolling windows, prior-year window, streak, third-set and tiebreak records), which tells the agent what analytics it will receive.

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?

Purpose is front-loaded in the opening clause, followed by a compact inventory of outputs and one routing sentence. It is dense and list-heavy, but each listed output earns its place because there is no output schema to carry that information.

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 must carry the return-value explanation, and it does so thoroughly enough for an agent to know what to expect. Filter behavior for level and round is left entirely to the schema, and response size or shape is not hinted at, leaving a minor 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%, so player_id, level, round, after_date and before_date are fully documented in the schema itself. The description only restates the default 180-day window and adds no filter syntax or semantics beyond that, making 3 the correct baseline.

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 the form of a player) and defines the measure precisely: actual results versus Elo-predicted results. That metric distinguishes it from generic stat siblings like show-player-stats without needing to name them.

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 an explicit prerequisite path for the required argument by naming search-players as the way to obtain player_id, and it documents the default window. It stops short of saying when to prefer this over show-player-stats or list-player-matches, so no explicit exclusions are offered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources