Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wta_tournament_seasons

Lists every WTA tournament calendar season currently offered, preserving source order so you can pick a season before querying its calendar.

Instructions

Discover WTA tournament calendar seasons. Returns every season currently offered by the tournament calendar, preserving source order. Historical calendar availability does not imply ranking-date availability.

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": "wta_tournament_seasons"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose two useful traits: the result is the complete set of seasons, and source ordering is preserved. It says nothing about how seasons are identified in the response, whether the results are cached, or how live ranking or calendar data relates to a returned season.

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?

The description is three short sentences, with the purpose front-loaded and the ordering guarantee stated early. The final caveat about historical calendar availability versus ranking-date availability is terse to the point of being cryptic, which slightly weakens clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is a zero-parameter listing endpoint with no output schema, so the description should sketch the return shape. It says the result is every season in source order but never indicates what a season looks like, for example a year, an ID, or a label. That leaves an agent guessing how to consume the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to document. The baseline of 4 applies, and the description correctly does not invent parameters.

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 states a specific verb and resource: "Discover WTA tournament calendar seasons" and "Returns every season currently offered by the tournament calendar." This clearly distinguishes it from data-bearing siblings such as wta_tournament_draws or wta_tournament_matches, though it never names a sibling explicitly.

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: an agent can infer this is the enumeration step that precedes per-season tournament lookups. There is no explicit statement of when to call it, or when to use a different seasons tool such as flashscore_tournament_seasons or sofascore_tournament_seasons.

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

Deploy Server

Other Tools