Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gosugamers_tournament_participants

Retrieve the teams entered in a GosuGamers tournament, including team names, logos, rankings, countries, and profile URLs by game and tournament ID.

Instructions

GosuGamers tournament participants. Returns the teams entered in one GosuGamers tournament: id, name, slug, logo, GosuGamers ranking, country and team URL. Both game and tournament_id are required; the upstream does not narrow the list by game, and an unknown tournament id returns an empty list. Take the tournament id from gosugamers-tournaments, gosugamers-matches or gosugamers-results and use a team id with gosugamers-team or gosugamers-team-results.

Input Schema

NameRequiredDescriptionDefault
gameYesGame section of the tournament; one of dota2, counterstrike, lol, valorant, mobile-legends, pubg-mobile, wild-rift, free-fire, battlegrounds-mobile-india
tournament_idYesNumeric tournament id from gosugamers-tournaments, gosugamers-matches or gosugamers-results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.5/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 real behavioral traits: unknown tournament id yields an empty list, and the upstream does not filter by game despite the required parameter. It never explicitly says the call is read-only or whether results paginate, which are the remaining gaps for a no-annotation tool.

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 sentences, front-loaded with what is returned and followed by the ID-provenance chain. Every sentence carries information; the opening fragment naming the tool is slightly redundant but functions as a topic sentence.

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?

No output schema exists, and the description compensates by listing the returned fields, plus edge-case behavior (empty list) and parameter caveats. Only pagination/result-size behavior and an explicit read-only statement are missing for a fully complete picture.

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 schema already documents both parameters and the enum; the baseline is 3. The description adds meaning beyond the schema by warning that `game` is required but functionally useless for narrowing, which the schema's own text does not say.

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 (returns) and resource (teams entered in one GosuGamers tournament), then enumerates the returned fields. This distinguishes it from gosugamers_tournament (single tournament detail) and gosugamers_tournament_talents (talent roster) without the agent needing to open the 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 where the tournament id comes from (gosugamers-tournaments, gosugamers-matches, gosugamers-results) and which tools consume the resulting team id (gosugamers-team, gosugamers-team-results). It also preempts a likely misuse — passing only a game — by stating that game does not narrow the list.

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