Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

wta_match_states

Lists accepted WTA match-feed state query values and labels, helping you map U, L, and C to raw MatchState responses without altering them.

Instructions

Discover WTA match-feed state selectors. Lists the accepted native state query values and labels. Query states U,L,C differ from raw response MatchState values; response values are retained unchanged.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does reasonably well: it discloses that the tool returns labels alongside values, and it flags the non-obvious asymmetry where query states (U,L,C) do not match raw response MatchState values, which the response preserves unchanged. It does not explicitly state the operation is read-only, but 'Discover'/'Lists' makes that clear enough.

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, front-loaded with the purpose, then the return contents, then the caveat. Every sentence adds information; the only mild overlap is between 'Discover ... state selectors' and 'Lists the accepted native state query values and labels.'

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 zero-parameter reference tool with no output schema, the description covers what the tool is, what it returns (values and labels), and the key naming distinction an agent would otherwise get wrong. Minor gap: it gives no example values or indication of how many states exist.

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. The baseline for a parameterless tool applies, and no contradictory or misleading parameter guidance is present.

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: it enumerates the accepted WTA match-feed state query values and labels. An agent can tell this is a lookup/enumeration tool, not a data-fetch tool, though it does not explicitly contrast itself with siblings like wta_countries or wta_tournament_matches.

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 implied: consult this to learn which state selector values are valid before filtering a match feed. The caveat that query states U,L,C differ from raw response MatchState values is genuinely useful guidance, but there is no explicit when-not or named alternative to call instead.

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

Deploy Server