Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

gosugamers_matches

Read-only

Returns upcoming and live esports matches from GosuGamers for one game (dota2, counterstrike, lol, valorant, mobile-legends, pubg-mobile, wild-rift, free-fire, battlegrounds-mobile-india) or all games: start time, tournament, stage, round, both teams and match URL; total_rows shows the full list size. Defaults to 10 per page; page and page_size (up to 100) read further pages. Use gosugamers_match with the returned tournament id and match id.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gosugamers_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNoOptional game section: dota2, counterstrike, lol, valorant, mobile-legends, pubg-mobile, wild-rift, free-fire or battlegrounds-mobile-india. Omit for all games.
pageNoOptional 1-based page. Page 1 with the default size comes from the public page; any other page or size uses the site's JSON API.
page_sizeNoOptional page size 1 to 100, default 10.

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.2/5.0
Behavior4/5

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

Annotations already mark it readOnly and open-world; the description adds useful behavior beyond them: default 10 per page, cap of 100, total_rows reporting full list size, and the cross-reference to the match detail tool. It stops short of describing ordering or rate limits.

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?

Dense but front-loaded: purpose first, then returned fields, pagination, and the follow-up pointer. Every clause is informative, though the inline game enumeration makes the opening sentence heavy.

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 100% schema coverage, an output schema, and safety annotations, the description covers everything an agent needs: scope, filtering, pagination defaults and limits, returned fields, and the next tool to call.

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 enums, page, and page_size. The description largely restates these values, adding only the semantic note that page/page_size 'read further pages' and clarifying what total_rows represents (which is output, not input). 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 and resource ('Returns upcoming and live esports matches from GosuGamers') with scope (one game or all games) and enumerates the returned fields. It distinguishes itself from the sibling gosugamers_results by emphasizing upcoming/live, and points to gosugamers_match for detail.

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?

Clear on how to use: omit game for all games, use page/page_size for further pages, and call gosugamers_match with returned tournament/match ids for follow-up. It does not explicitly say when NOT to use it (e.g., vs gosugamers_results for finished matches), so not a full 5.

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