Skip to main content
Glama
Sign In

Padel Analyst

by org.padelapi
OverviewDiscussionsAdmin

search-pairs

Read-onlyIdempotent

List pairs of professional padel players that have played at least one match together. Returns the pair ID, players, status (current if it is the active pairing of both players, former otherwise), combined ranking points (only for current pairs) and the dates of their first and most recent match together.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search-pairs"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoPair ID(s) to retrieve, comma-separated (e.g. `65-66,12-34`). Each pair ID is the two player IDs joined by a hyphen in ascending order.
pageNoPage number for pagination. Results are paginated: check `meta` (`current_page`, `last_page`, `total`) in the response and request further pages with this parameter until you have all the results you need.
statusNoStatus of the pair: `current` if it is the active pairing of both players, `former` otherwise.
sort_byNoName of the parameter to sort the pairs by, always descending. Defaults to `last_match_at` (date of their most recent match together). With `points`, pairs without points go last.last_match_at
categoryNoCategory of the pair. Either `men` or `women`.
per_pageNoNumber of results per page (1-50). Use a small value when you only need the top results, or 50 to minimize pages when you need the complete list.
after_dateNoDate after which the pair has played a match in `YYYY-MM-DD` format. Pairs without matches in the range are excluded.
before_dateNoDate before which the pair has played a match in `YYYY-MM-DD` format.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / sort_by / description
      Previous value: -"Name of the parameter to sort the pairs by. Defaults to `last_match_at` (date of their most recent match together, desc)."New value: +"Name of the parameter to sort the pairs by, always descending. Defaults to `last_match_at` (date of their most recent match together). With `points`, pairs without points go last."
    • changedInput schema / properties / sort_by / enum
      Previous value: -[
-  "last_match_at",
-  "first_match_at"
-]New value: +[
+  "last_match_at",
+  "first_match_at",
+  "points"
+]
    • addedInput schema / properties / status
      Added value: +{
+  "description": "Status of the pair: `current` if it is the active pairing of both players, `former` otherwise.",
+  "enum": [
+    "current",
+    "former"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / per_page / description
      Previous value: -"Number of results per page (1-50). Use a small value when you only need the top results (e.g. 1 for the most recent match), or 50 to minimize pages when you need the complete list."New value: +"Number of results per page (1-50). Use a small value when you only need the top results, or 50 to minimize pages when you need the complete list."
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: the exact result fields, the meaning of the two status values, and the non-obvious rule that ranking points only exist for current pairs. It omits pagination behavior, though the schema covers that.

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, front-loaded with purpose and scope, then a compact enumeration of return fields. Every clause carries information and nothing is repeated or padded.

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 an eight-parameter, fully documented read tool with no output schema, the description is largely self-sufficient because it explains the shape of a returned pair. It doesn't mention pagination or default sorting, but those are handled in the schema, so the gap is small.

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?

With 100% schema description coverage, the schema already documents id, page, status, sort_by, category, per_page, after_date and before_date in detail. The description restates the status and points semantics almost verbatim from the schema rather than adding new meaning, so the 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?

The description gives a specific verb and resource ('List pairs of professional padel players') plus a meaningful scope constraint ('that have played at least one match together'), so an agent can distinguish this from search-players or match-level tools. It stops short of naming a sibling to route away from, which keeps it from a 5.

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

Usage Guidelines3/5

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

Usage is only implied: the scope clause suggests this is for enumerating existing pairings, and the participant fields suggest discovery rather than lookup. There is no explicit when-to-use, no exclusion, and no named alternative such as show-pair-stats for detailed pair metrics.

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

All Padel Analyst toolsInspect
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