Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gosugamers_results

Retrieve recent completed esports match results by game or across all games, including final scores, winner flags, pagination, and total result counts for scoreboard checks.

Instructions

GosuGamers recent esports match results. Returns the most recent completed 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, with final scores and winner flags. total_rows reports how many results the site lists. Use gosugamers-match with the returned ids for opponents, ranking and streams.

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

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations, so the description carries the disclosure burden and does well: it names pagination defaults (10, up to 100), the returned content (final scores, winner flags), and the total_rows count. It stops short of describing ordering guarantees or failure/empty behavior, so not 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.

Conciseness5/5

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

Four tight sentences, front-loaded with the purpose, then coverage, then pagination, then the handoff. Nothing is redundant given the 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?

With no output schema, the description usefully names key return fields (scores, winner flags, total_rows) and points to the detail tool for enrichment. Minor gap: it doesn't clarify how these results differ from the broader gosugamers_matches listing.

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%, including enum values and the page/page_size ranges, so the schema already does the work. The description restates defaults rather than adding new semantics beyond format, which matches the baseline 3.

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+resource ('recent completed esports match results') and scopes it precisely (one game or all games). It implicitly separates itself from gosugamers_matches and gosugamers_match by emphasizing 'completed' and by naming the detail tool for follow-up.

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?

Explicitly routes the agent onward: 'Use gosugamers-match with the returned ids for opponents, ranking and streams.' The when-to-use-this side is clear (recent finished matches), but the exclusion versus gosugamers_matches (scheduled/all matches) is left to inference.

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