Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gosugamers_matches

Fetch upcoming and live GosuGamers esports matches by game or across all games, with pagination, returning teams, tournaments, start times, and match URLs.

Instructions

GosuGamers upcoming and live esports matches. Returns the next upcoming and currently live esports matches from GosuGamers, for one game or across all games, 10 per page by default and up to 100 with page and page_size: start time, tournament, stage, round, both teams and the match URL. total_rows reports how many matches the site lists. Use gosugamers-match with the returned tournament and match ids.

Input Schema

NameRequiredDescriptionDefault
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; page 1 with the default size is read from the public page, any other page or size from the site's JSON API; defaults to 1
page_sizeNoPage size, 1 to 100; defaults to 10

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?

No annotations, so the description carries the burden and does well: it discloses the returned fields (start time, tournament, stage, round, teams, match URL), the default page size and 100 cap, and that total_rows reports the site's total. It doesn't cover freshness/refresh cadence or any access constraints, which limits it short of a 5.

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?

A single dense, front-loaded paragraph that leads with what is returned and follows with pagination and the follow-up tool. Efficient overall, though several clauses duplicate schema content and add length.

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?

For a 3-param read-only listing tool with no output schema and no annotations, the description supplies the return shape, pagination behavior, total_rows meaning, and the next-step tool. It omits the page-1-vs-API detail present only in the schema, but is otherwise complete enough to invoke correctly.

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 coverage is 100%, so the schema already documents game enum, page, and page_size. The description largely restates the defaults and ranges ('10 per page by default and up to 100 with page and page_size'; 'for one game or across all games') rather than adding new semantics, so the baseline 3 is appropriate.

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?

States a specific verb and resource: returns the next upcoming and currently live esports matches from GosuGamers, scoped to one game or all games. The 'upcoming and live' framing clearly sets it apart from a results tool, though it never explicitly contrasts with the sibling gosugamers_results, which is the nearest confusion point.

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?

Implies the usage context (fetch upcoming/live matches, optionally per game) and points to gosugamers-match as the logical follow-up using the returned ids. It stops short of stating when NOT to use it, e.g. that past matches belong to gosugamers_results.

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