Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

gosugamers_match

Read-only

Returns one GosuGamers esports match: start time, tournament, stage, round, best-of, finished flag, opponents with score, placement, world ranking and country, number of games and linked streams with language and viewer count. Requires game, tournament_id and match_id from gosugamers_matches or gosugamers_results; a mismatched tournament returns not found. Battle-royale titles can have more than two opponents. The games list gives each game id for gosugamers_match_game.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "game": "<game>",
      "tournament_id": "<tournament_id>",
      "match_id": "<match_id>"
    },
    "name": "gosugamers_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameYesRequired game section: dota2, counterstrike, lol, valorant, mobile-legends, pubg-mobile, wild-rift, free-fire or battlegrounds-mobile-india.
match_idYesRequired numeric match id from gosugamers_matches or gosugamers_results.
tournament_idYesRequired numeric tournament id (tournament.id) from gosugamers_matches or gosugamers_results.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Goes beyond readOnlyHint/openWorldHint by disclosing that a mismatched tournament_id returns not found, that battle-royale titles can have more than two opponents, and that streams carry language and viewer count. These are real behavioral quirks an agent must plan around; no pagination or rate-limit context is given, but the annotations carry the safety profile.

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?

Four sentences, front-loaded with the return payload first, then prerequisites, then caveats. The field enumeration is dense but each clause (streams, battle-royale caveat, game id linkage) carries distinct information; only slight trimming would improve it.

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?

An output schema exists so return-value explanation is bonus rather than required, yet the description still covers payload shape, error behavior on mismatch, data-shape edge cases, and the downstream call into gosugamers_match_game. Nothing an agent needs in order to call it 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?

Schema coverage is 100%, so baseline is 3, but the description adds value the schema lacks: that tournament_id and match_id must be paired consistently (mismatch yields not found) and that match_id can originate from either of two sibling endpoints. It also warns about variable opponent counts, which the schema does not imply.

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 esports match') and immediately enumerates the returned fields, making clear this is the single-match detail endpoint rather than the list endpoints gosugamers_matches or gosugamers_results. The 'one match' scope distinguishes it from its siblings without the agent needing to open a 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 three required inputs must come from gosugamers_matches or gosugamers_results, which is genuine prerequisite routing, and points to gosugamers_match_game for per-game data. It does not spell out an explicit when-not-to-use case (e.g. use gosugamers_results for finished-match lists), leaving that to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources