Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gosugamers_match_game

Fetch detailed data for one GosuGamers match game by game_id, including map, scores, picks or bans, lineups, round scores, placements, kills, points, and VODs.

Instructions

GosuGamers single game (map) of a match. Returns one game of a GosuGamers match: the map, each team's score, side and first-pick flag, the picks or bans with the player (agents, heroes or champions where the title publishes them), the lineups, round or half scores (Counter-Strike and Valorant), every team's placement, kills and points for battle-royale games (PUBG Mobile) and VODs. Take game_id from the games list of gosugamers-match. Fields a title does not publish are empty. An unknown game id returns not found.

Input Schema

NameRequiredDescriptionDefault
game_idYesNumeric game id from the games list of gosugamers-match

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 are provided, so the description carries the full burden and largely meets it: it enumerates the returned payload (map, scores, sides, picks/bans, lineups, round scores, battle-royale stats, VODs), discloses that unpublished fields come back empty, and states that an unknown id yields not found. It stops short of describing whether data is live vs. final or any coverage caveats across titles.

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 one-line purpose before the field inventory, and every clause is substantive. The field enumeration is long but necessary given there is no output schema; a small amount of compression is possible but nothing is filler.

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 annotations, the description supplies everything an agent needs: what entity it's keyed on, where the id comes from, the shape of the return across multiple game genres, how missing fields behave, and the not-found failure mode. Nothing material is left to inference.

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% and the single parameter's schema text already says 'Numeric game id from the games list of gosugamers-match'. The description repeats that provenance almost verbatim rather than adding format, range, or lookup guidance, so baseline 3 is appropriate.

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: returns one game (map) of a GosuGamers match, with an explicit parenthetical clarifying 'game' means 'map'. It is clearly scoped as a child of gosugamers_match, so an agent can distinguish it from the match-level sibling without opening either schema.

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 states the prerequisite: 'Take `game_id` from the `games` list of gosugamers-match', which routes the agent to the parent tool first. It does not state a when-not condition or name any alternate sibling directly, but the dependency chain makes the usage context unambiguous.

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