Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wta_tournament_draws

Retrieve all published WTA tournament draws—singles, doubles, and qualifying—by group ID and season, returning native nested JSON as structured bracket data with seeds, byes, scores, and rounds.

Instructions

Read a WTA tournament draw resource. Returns all event draws published in the native tournament resource, including available singles, doubles and qualifying draws. Decodes the native nested JSON into objects while preserving field case, cardinality, scores, seeds, byes, groups and source round data. Native null draw data remains null. UI tab/round choices do not add server filters or computed bracket advancement.

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": {
      "group_id": "<group_id>",
      "year": "<year>"
    },
    "name": "wta_tournament_draws"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesNative season from tournament season discovery
group_idYesNative tournament group ID from the calendar

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses meaningful behavioral details: it returns all published draws, decodes native nested JSON while preserving field case, cardinality and structural elements, treats native nulls as null, and notes that UI tab choices do not add server filters or computed advancement. Missing details such as authentication, rate limits, or pagination prevent a 5.

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 front-loaded with the core return behavior and uses compact sentences. A few phrases, such as the closing note about UI tab/round choices, are slightly oblique but still relevant to data interpretation.

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?

Because there is no output schema, the description must explain return values and does so reasonably well by describing decoded draw objects, preserved field structure, and null handling. It lacks any error or pagination context, which keeps it from a 5 for a read tool.

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%, so the baseline is 3. The description does not add any meaning beyond the schema's own explanations for year and group_id; it merely describes the native resource shape.

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 ('Read') and resource ('WTA tournament draw') and clarifies the scope by listing singles, doubles and qualifying draws. It does not explicitly differentiate itself from siblings such as wta_tournament or flashscore_tournament_draw, so it falls short of 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 Guidelines2/5

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

The description explains what the tool returns but gives no guidance on when to use it versus alternatives like wta_tournament, wta_tournament_matches, or flashscore_tournament_draw. No prerequisites or exclusions are stated.

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