Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gosugamers_match

Retrieve a GosuGamers esports match by game, tournament ID, and match ID to get start time, stage, opponents and scores, placement, rankings, streams, and game IDs for follow-up lookups.

Instructions

GosuGamers esports match detail. Returns one GosuGamers match: start time, tournament, stage, round, best-of, finished flag, both opponents with score, placement, world ranking and country, the number of games in the series and linked streams with language and viewer count. All of game, tournament_id and match_id are required; an id that does not belong to the stated tournament returns not found. Battle-royale titles can list more than two opponents. The games list gives each game's id for gosugamers-match-game.

Input Schema

NameRequiredDescriptionDefault
gameYesGame section; one of dota2, counterstrike, lol, valorant, mobile-legends, pubg-mobile, wild-rift, free-fire, battlegrounds-mobile-india
match_idYesNumeric match id from gosugamers-matches or gosugamers-results (id)
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

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the error behavior ('an id that does not belong to the stated tournament returns not found') and the edge case that battle-royale titles can return more than two opponents. It does not mention auth, rate limits, or staleness of live scores, which would be the remaining behavioral gaps.

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?

Front-loaded with the identifying sentence, then payload contents, then constraints and the sibling handoff. The long field enumeration is dense but justified because there is no output schema; no sentence is filler.

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 and no annotations, so the description must cover both return shape and behavior, and it largely does: it enumerates returned fields, describes the not-found case, and notes the battle-royale exception. Minor gaps remain around permissions/auth and whether stream viewer counts are live or snapshotted.

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 is 3, but the description adds a genuine cross-parameter constraint absent from the schema: match_id and tournament_id must be consistent or the call returns not found. It also flags that opponent cardinality varies by game title, which affects how the returned opponent fields should be read.

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 and resource ('Returns one GosuGamers match') and then enumerates the exact payload fields, so the agent knows precisely what comes back. It also distinguishes itself from the sibling gosugamers-match-game by naming what that tool consumes ('The `games` list gives each game's id for gosugamers-match-game').

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?

Explains that all three ids are required together and that a mismatched id yields not found, which is the key precondition for calling it, and routes to gosugamers-match-game for per-game detail. It stops short of an explicit 'use gosugamers_matches/gosugamers_results first to obtain ids, not this tool', leaving that inference to the schema text.

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