Crawlora MCP

gosugamers_tournaments

Read-only

Lists GosuGamers esports tournaments, optionally for one game (dota2, counterstrike, lol, valorant, mobile-legends, pubg-mobile, wild-rift, free-fire, battlegrounds-mobile-india) and one state (all, ongoing, upcoming, past) with an optional name prefix q: id, name, status, start time, prize pool with currency and USD value, participant count and URL. Paged with page and page_size up to 100; total_rows is the filtered list size. Use gosugamers_tournament with a returned id for stages and upcoming matches.

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

Input Schema

Name	Required	Description
`q`	No	Optional tournament name prefix, for example VCT.
`game`	No	Optional game section: dota2, counterstrike, lol, valorant, mobile-legends, pubg-mobile, wild-rift, free-fire or battlegrounds-mobile-india. Omit for all games.
`page`	No	Optional 1-based page, default 1.
`state`	No	Optional state: all (default), ongoing, upcoming or past.
`page_size`	No	Optional page size 1 to 100, default 10.

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.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds pagination behavior (page/page_size up to 100) and the meaning of total_rows as the filtered list size. That is real context beyond the annotations, though nothing is said about ordering or rate limits.

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 the verb and resource, then filters, then pagination and routing. The long parenthetical game enumeration is the bulkiest part but it is genuinely useful value information, so little is wasted.

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 read-only paged list with an output schema, the description covers filters, pagination, the semantics of total_rows, and the handoff to the detail tool. Nothing an agent needs 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all five parameters, including the game and state value lists that the description restates. The description adds only marginal meaning (q as a name prefix, page_size cap) beyond what the schema provides, so the baseline 3 applies.

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 ('Lists GosuGamers esports tournaments') plus the exact filter dimensions (game, state, name prefix) and returned fields. It also names the sibling detail tool gosugamers_tournament, so an agent can separate list from detail without opening either schema.

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?

Gives explicit routing: use gosugamers_tournament with a returned id for stages and upcoming matches, which tells the agent when to move on. It also clarifies that game/state/q are optional filters (omit for all). It does not distinguish this list from other GosuGamers siblings such as gosugamers_matches or gosugamers_results.

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?