Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gosugamers_tournaments

List and filter GosuGamers esports tournaments by game, state, or name prefix, returning IDs, status, start times, prize pools, participants, and URLs with pagination.

Instructions

GosuGamers esports tournament directory. Lists GosuGamers esports tournaments, optionally for one game and one state (all, ongoing, upcoming, past), with an optional name prefix q: id, name, game, status, start time, prize pool with currency and USD value, participant count, featured flag and the tournament URL. Paged with page and page_size (up to 100); total_rows reports the size of the filtered list. Use gosugamers-tournament with a returned id and game for stages and upcoming matches.

Input Schema

NameRequiredDescriptionDefault
qNoTournament name prefix, up to 100 characters
gameNoGame section; one of dota2, counterstrike, lol, valorant, mobile-legends, pubg-mobile, wild-rift, free-fire, battlegrounds-mobile-india; omit for all games
pageNo1-based page; defaults to 1
stateNoTournament state; one of all, ongoing, upcoming, past; defaults to all
page_sizeNoPage size, 1 to 100; defaults to 10

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.3/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 disclose the returned field set, the paging contract ("up to 100"), and that `total_rows` reports the size of the filtered list rather than the whole directory. It omits sort order and data freshness, which matter for a directory listing, so it is strong but not complete.

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?

Front-loaded identification, then filters, then return shape, then pagination, then the hand-off to the sibling — a sensible order with no filler sentences. The mid-sentence field enumeration is dense and could be a list, keeping it just below top marks.

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?

There is no output schema, and the description compensates by enumerating the returned fields and the pagination envelope, which is enough to call the tool and interpret the response. Missing sort order is the one gap an agent might reasonably still have.

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 enums, prefix semantics and defaults are already documented. The description adds only marginal meaning beyond the schema — that only one game and one state may be supplied — so 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 optional scoping filters and the exact shape of the returned record. An agent can distinguish this directory-listing tool from bo3_tournaments, lolesports_tournaments and gosugamers_tournament without opening a schema.

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?

Explicitly names the downstream alternative and the condition that selects it: "Use gosugamers-tournament with a returned id and game for stages and upcoming matches." It also signals that filtering is limited to one game and one state, which tells the agent this is the browse step of a two-step flow.

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