Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

wta_countries

Read-only

List the complete country and region vocabulary the WTA player rankings use: each three-letter WTA code (IOC-style, so ALG is Algeria and not ISO DZA) with its display label. ALL, the first entry, means the ranking nationality filter is unset. Use this first to get a valid country for wta_rankings; the vocabulary applies to the singles, doubles and race-singles player views, while race-doubles has no country selector. Takes no input.

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

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuinely non-obvious behavior: that ALL is the first entry and signals an unset nationality filter, and that the code space is IOC rather than ISO. With an output schema present, no return-value description is owed, though it doesn't state whether the list is paged or its approximate size.

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?

Four tightly packed sentences that lead with the resource and end with usage, with zero filler prose. The final clause "Takes no input" is the one piece that duplicates structured data rather than earning its place.

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

Completeness5/5

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

For a no-argument vocabulary lookup with an output schema, everything an agent needs is present: what the list contains, the code-format pitfall, the meaning of the sentinel entry, and which downstream tool and views it feeds. Nothing material is missing.

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?

Zero parameters gives a baseline of 4; the trailing "Takes no input" merely restates the empty schema object and adds no new meaning. No parameters means there is nothing further to disambiguate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb and resource ("List the complete country and region vocabulary the WTA player rankings use"), plus the exact shape of each entry (three-letter WTA/IOC-style code + display label). It also pre-empts a likely confusion by stating ALG is IOC-style rather than ISO DZA, and names its consumer tool wta_rankings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicit sequencing guidance ("Use this first to get a valid country for wta_rankings") with the applicable scope enumerated: singles, doubles and race-singles, while race-doubles has no country selector. It states when to call it and where its output is and is not valid.

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

All Crawlora MCP toolsInspect
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