Padel Analyst

simulate-match

Read-onlyIdempotent

Simulate a match between players from two teams. Provide player IDs for both teams (use the "search-players" tool to get them). Returns: name (of the match), probability (win probability of team_1 and team_2 as a percentage), favorite ("team_1" or "team_2", null if evenly rated), elo_diff (Padel API Elo gap between the teams), played_at (day the simulation is rated for) and players (the full player details per team).

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": {
      "team_1": "<team_1>",
      "team_2": "<team_2>"
    },
    "name": "simulate-match"
  }
}

Input Schema

Name	Required	Description
`team_1`	Yes	List of player IDs for team 1
`team_2`	Yes	List of player IDs for team 2
`played_at`	No	Day the match would be played, as YYYY-MM-DD. Players are rated with the Elo they had entering that day, so you can replay a past match-up with the ratings of the time. Optional, defaults to today.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful return context: win probability, favorite, Elo gap, rated day, and full player details, which is valuable because there is no output schema.

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?

The description is compact and front-loaded: purpose first, input guidance second, return fields third. Every sentence contributes useful information.

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?

With no output schema, the description compensates by listing the key return fields. Combined with annotations and fully documented parameters, it gives enough information for an agent to invoke the tool correctly.

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 the schema already explains team_1, team_2, and the played_at date semantics in detail. The description reinforces the need for player IDs but does not add parameter meaning beyond what the schema already provides, so the high-coverage baseline of 3 applies.

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?

The description states a specific verb and resource: simulate a match between players from two teams. This clearly distinguishes it from sibling search/list/stats tools, which retrieve data rather than run a simulation.

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 explicitly says to provide player IDs for both teams and points to the search-players tool for obtaining them. It does not name exclusion cases or alternatives for the simulation itself, but the intended use is clear.

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?