Crawlora MCP

gosugamers_tournament

Read-only

Returns one GosuGamers esports tournament: name, status, start time, description, LAN flag, venue, country, USD prize pool when listed, sponsors, stages with status and the next upcoming matches. Requires game and tournament_id (from gosugamers_matches or gosugamers_results); a tournament of another game returns not found.

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": {
      "game": "<game>",
      "tournament_id": "<tournament_id>"
    },
    "name": "gosugamers_tournament"
  }
}

Input Schema

Name	Required	Description	Default
`game`	Yes	Required game section: dota2, counterstrike, lol, valorant, mobile-legends, pubg-mobile, wild-rift, free-fire or battlegrounds-mobile-india.
`tournament_id`	Yes	Required numeric tournament id from gosugamers_matches or gosugamers_results.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, so the description's added value is the failure mode: a tournament from another game returns not found, and the prize pool is present only "when listed." These are useful edge-case disclosures beyond the annotations.

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?

Two sentences, front-loaded with what is returned, then requirements and the not-found caveat. The field enumeration is dense but each clause conveys a distinct capability.

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?

An output schema exists, so listing return fields is not strictly needed, but it orients the agent quickly; combined with the id provenance and not-found behavior, nothing needed to call it correctly 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?

Schema coverage is 100%, so the baseline is 3, but the description adds cross-parameter meaning: the id must originate from gosugamers_matches/results and must belong to the supplied game or the call fails. That constraint isn't visible in the schema.

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?

States a specific verb and resource ("Returns one GosuGamers esports tournament") and enumerates the payload (status, start time, venue, prize pool, stages, next matches), making it clearly distinct from the sibling list tool gosugamers_tournaments.

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?

Explains that game and tournament_id are required and where the id comes from (gosugamers_matches or gosugamers_results). It doesn't explicitly point to gosugamers_tournaments as the list alternative, but the usage context is genuinely clear.

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

All Crawlora MCP tools Inspect

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

Need Help?