Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

gosugamers_tournament_participants

Read-only

Returns the teams entered in one GosuGamers esports tournament: id, name, slug, logo, GosuGamers ranking, country and team URL. Requires game (dota2, counterstrike, lol, valorant, mobile-legends, pubg-mobile, wild-rift, free-fire, battlegrounds-mobile-india) and tournament_id from gosugamers_tournaments, gosugamers_matches or gosugamers_results; the game does not narrow the list and an unknown tournament returns an empty list. Use a team id with gosugamers_team or gosugamers_team_results.

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>"
    },
    "name": "gosugamers_tournament_participants"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameYesRequired game section: dota2, counterstrike, lol, valorant, mobile-legends, pubg-mobile, wild-rift, free-fire or battlegrounds-mobile-india.
tournament_idYesRequired numeric tournament id from gosugamers_tournaments, 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.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful behavioral detail beyond annotations: the game does not narrow the list, an unknown tournament returns an empty list, and the response includes ranking/country/URL fields.

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?

The description is front-loaded with the primary action and packs return fields, required inputs, input sources, edge behavior, and follow-up tool routing without wasted sentences.

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 an output schema available and full schema description coverage, the description still adds the key context an agent needs: what is returned, where tournament_id comes from, that game does not filter, and that unknown tournaments yield an empty list.

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 a baseline of 3 would apply. The description adds meaningful semantics beyond the schema by noting that the game parameter does not narrow the result list and by specifying which sibling tools supply tournament_id.

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 the teams entered in one GosuGamers esports tournament.' It also lists the returned fields and routes team-level lookups to gosugamers_team/gosugamers_team_results, so the tool is clearly distinguishable from team-detail and tournament-list siblings.

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?

Gives clear prerequisites (game and tournament_id) and names the sibling tools that can supply tournament_id. It also explains that a team id should be used with gosugamers_team or gosugamers_team_results, though it does not explicitly contrast this tool with every nearby sibling such as stage_groups or tournament_talents.

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