Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gosugamers_games

Lists available GosuGamers game sections with display names and slugs, so you can choose the correct game value for match-related endpoint requests.

Instructions

GosuGamers game sections. Returns the game sections whose match pages this API reads: dota2, counterstrike, lol, valorant, mobile-legends, pubg-mobile, wild-rift, free-fire and battlegrounds-mobile-india, with display names. Use a slug as game in the other gosugamers endpoints.

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations exist, so the description carries the burden; it does disclose the return shape ('game sections ... with display names') and implicitly establishes this as a passive lookup with no mutation. It omits any statement about side effects, auth, or caching, but the enumerable static content makes that low-risk.

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 resource identity, then the concrete value list, then the downstream instruction. Nothing is padded and every clause carries information an agent would otherwise have to guess.

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?

With no output schema and no parameters, the description must describe the return itself, and it does: the enumerated slugs plus display names. Nothing needed to call or interpret this tool 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?

Zero parameters, so the baseline is 4. The description adds cross-tool value by defining the meaning of the `game` parameter accepted by sibling endpoints and supplying the full valid value set, which the empty input schema cannot convey.

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 resource ('GosuGamers game sections') and then enumerates exactly what it returns — nine slugs plus display names. An agent knows precisely what this yields without opening anything else, and it is clearly distinct from the sibling match/tournament/team endpoints.

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?

The closing sentence explicitly routes usage: 'Use a slug as `game` in the other gosugamers endpoints,' which tells an agent this is the discovery step before calling gosugamers_matches, gosugamers_results, etc. It lacks an explicit when-not or a named alternative, keeping it short of a 5.

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