Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wta_tournament

Retrieves a WTA tournament season using group ID and year, returning native season metadata, live scoring identifier, and published singles/doubles champions.

Instructions

Read a WTA tournament season. Returns the tournament's native season metadata, live scoring identifier and published singles/doubles champions. Group and season-specific levels remain separate. Use the tournament calendar and season discovery for IDs and years.

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

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.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; 'Read' plus the return list makes the non-mutating, lookup nature clear. However, it says nothing about behavior on invalid IDs, unpublished champions (null vs omitted), or whether live scoring identifiers can be absent, which matters for an unannotated tool.

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?

Purpose and return contents are front-loaded in the first two sentences, and the sourcing hint follows logically. The third sentence ('Group and season-specific levels remain separate') is terse to the point of being cryptic, but no sentence is pure filler.

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 two-parameter read lookup with no output schema and no annotations, the description covers what is returned and where the IDs come from, which is enough to call it correctly. Only edge-case behavior (missing champions, invalid group/season pairing) is left unstated.

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% and both parameter descriptions already say 'Native season from tournament season discovery' and 'Native tournament group ID from the calendar'. The description adds only the conceptual note that group and season levels stay separate, which is marginal 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 ('Read') and resource ('WTA tournament season') and enumerates what comes back: native season metadata, live scoring identifier, and published singles/doubles champions. This differentiates it from draw/match/player siblings, though no sibling is named explicitly as an alternative.

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?

Explicitly directs the agent to obtain IDs and years from 'the tournament calendar and season discovery', which is actionable prerequisite guidance. It stops short of stating when not to use this tool or naming a concrete alternative sibling.

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