Skip to main content
Glama

Padel Analyst

show-pair-synergy

Read-onlyIdempotent

Get the synergy of a pair of players by providing their player IDs: results together against what their Elo ratings predicted. Returns expected and actual win rate, the delta between them and matches played together, and the same values by quarter with their trend (rising, stable or declining). 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-synergy"
  }
}

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).
after_dateNoMeasure the synergy from matches played after this date (YYYY-MM-DD).
before_dateNoMeasure the synergy from matches played before this date (YYYY-MM-DD).
player_1_idYesThe ID of the first player in the pair.
player_2_idYesThe ID of the second player in the pair.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this a safe, read-only, idempotent, closed-world operation, so the safety profile is covered. The description adds genuine value by disclosing the shape of the result: expected vs actual win rate, their delta, matches played, and quarterly breakdown with a rising/stable/declining trend. However, with no output schema, it omits behavior an agent may need, such as what happens when the pair has no matches together or how the trend is derived.

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?

Three compact sentences with the purpose front-loaded, followed by outputs and then the ID-lookup pointer, so nothing is buried. The phrase 'results together against what their Elo ratings predicted' is slightly elliptical, but the surrounding sentences disambiguate it.

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?

For a six-parameter, read-only analytical tool with no output schema, the description is nearly complete: it states the computation, the returned metrics, and how to obtain required IDs. Only edge-case behavior (empty pair history, trend methodology) remains 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%, including enum values for round and the full level taxonomy, so the schema carries parameter meaning on its own; baseline 3 applies. The description only reinforces that player_1_id/player_2_id identify the pair, adding nothing about how after_date, before_date, level, or round reshape the computation.

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 operation on a specific resource: synergy for a pair of players, defined concretely as actual results versus Elo-predicted results. It distinguishes itself from generic listing tools by enumerating outputs (expected/actual win rate, delta, matches together, per-quarter trend), though it never names or contrasts with the close sibling show-pair-stats.

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?

It supplies explicit prerequisite guidance by telling the agent to use 'search-players' to obtain the required player IDs, which resolves the main blocker to invocation. It offers no exclusions or comparison against show-pair-stats, so the agent must infer when synergy is preferable to plain pair statistics.

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