Padel Analyst

search-seasons

Read-onlyIdempotent

Search seasons by ID or year. Returns each season with its name, start and end dates, status and number of tournaments. Seasons from 2023 onwards are available.

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-seasons"
  }
}

Input Schema

Name	Required	Description
`id`	No	Season ID(s) to retrieve, comma-separated (e.g. `1,2,3`).
`page`	No	Page 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.
`year`	No	Year of the season to filter by (2023 onwards).
`per_page`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026

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."

First observedOct 30, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds meaningful context beyond that: the exact return fields (name, dates, status, tournament count) and the hard availability limit of 2023 onwards, which prevents futile queries for older seasons.

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 short sentences, front-loaded with the action and filters, followed by the return shape and the availability constraint. Every clause carries information an agent would otherwise have to discover by calling the tool.

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 simple paginated read tool with full annotation coverage and complete parameter docs, the description covers purpose, filters, return fields, and data range. Pagination is only handled in the schema, but that is sufficient given its 100% coverage; no output schema exists, and the description compensates by naming the returned fields.

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 coverage is 100%, with id, year, page, and per_page all fully documented, including pagination mechanics and the 1-50 bound on per_page. The description only restates the ID/year filters and repeats the 2023 lower bound already in the year parameter, so it adds little beyond the schema.

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 ('Search seasons') plus the filter axes ('by ID or year'), so the agent knows exactly what this returns. It does not explicitly contrast itself with siblings like search-tournaments or search-players, but the resource is distinct enough that confusion is unlikely.

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 implied: use it to find seasons, filtered by ID or year, and note the data only starts in 2023. There is no explicit when-to-use/when-not framing or pointer to any alternative tool, and no mention of what to do if a season is not found.

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?