Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gosugamers_tournament

GosuGamers esports tournament detail. Returns one GosuGamers tournament: name, status, start time, description, LAN flag, venue and country, prize pool in USD when listed, sponsors, stages with their status and the next upcoming matches.

Instructions

GosuGamers esports tournament detail. Returns one GosuGamers tournament: name, status, start time, description, LAN flag, venue and country, prize pool in USD when listed, sponsors, stages with their status and the next upcoming matches. A tournament that belongs to a different game than game returns not found.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.9/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 the full return shape (name, status, start time, LAN flag, venue/country, USD prize pool "when listed", sponsors, stages, next upcoming matches) and one important failure mode — a tournament belonging to a different game than `game` returns not found. It does not mention permissions, rate limits, or caching, but for an unauthenticated public read those are minor.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the identity of the tool, followed by the payload contents and the one edge case. The field enumeration is long but earns its place because there is no output schema.

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, so documenting the returned fields is exactly the right compensation, and the not-found rule covers the main error path. What is missing is any hint that ids come from gosugamers-matches/gosugamers-results (that lives only in the schema) and any note on whether stage/match data is nested or partial.

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 would be 3. The description adds real meaning beyond the schema by stating the semantic constraint on `game`: an id from a different game section resolves to not found, which tells the agent the two parameters must be consistent.

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?

The description opens with a specific verb+resource combination ("Returns one GosuGamers tournament") and enumerates the fields returned, so it is clearly a single-item detail lookup rather than a listing. It does not explicitly name the sibling list tool (gosugamers_tournaments) or participant/talent siblings, so differentiation is implied by "one" rather than stated.

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 by the singular-detail framing plus the note that the id comes from a matches/results context (in the schema). There is no explicit "use this instead of X when Y" guidance and no statement of when a caller should prefer gosugamers_tournaments or the participant sub-resources.

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