Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wta_countries

Retrieve WTA ranking country and region codes and labels for player nationality filters, with ALL to omit filtering; team race rankings lack a country selector.

Instructions

Discover WTA ranking country and region codes. Returns the source codes and labels used by player rankings. ALL omits the nationality filter. Team race rankings do not have a country selector.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the return payload ('source codes and labels') and two scoping caveats, which is solid for a static zero-parameter lookup, but says nothing about ordering, size, or the exact shape of returned entries.

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?

Three short sentences with the purpose front-loaded and the caveats trailing. Every sentence adds information; 'Discover' is slightly marketing-flavored but not wasteful.

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?

For a trivial zero-parameter lookup this is mostly adequate: it says what the tool returns and where it does not apply. Without an output schema, however, the description should say more about the returned structure (e.g., code/label pairs versus arrays) so the agent knows 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 nothing for the description to disambiguate. Baseline of 4 applies; the mention of 'ALL' is a caveat about a value the caller passes elsewhere, not an actual parameter of this tool.

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: 'Discover WTA ranking country and region codes', and clarifies these are the codes used by player rankings. It is clearly a reference/lookup tool, distinguishable from data-fetching siblings like wta_rankings, though it never explicitly names a consumer tool.

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?

Provides real when/when-not context: 'ALL omits the nationality filter' explains the special sentinel value, and 'Team race rankings do not have a country selector' tells the agent where these codes do not apply. It stops short of explicitly telling the agent to call this before filtering wta_rankings.

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