Crawlora MCP

gosugamers_tournament_talents

Read-only

Returns the casters, hosts and analysts assigned to one GosuGamers esports tournament: id, name, game, roles (for example Host, Commentator, Analyst), broadcast language code, country, image and profile URL. Requires tournament_id from gosugamers_tournaments, gosugamers_matches or gosugamers_results; a tournament with no listed crew returns an empty list.

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": {
      "tournament_id": "<tournament_id>"
    },
    "name": "gosugamers_tournament_talents"
  }
}

Input Schema

Name	Required	Description	Default
`tournament_id`	Yes	Required numeric tournament id from gosugamers_tournaments, gosugamers_matches or gosugamers_results.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4/5.0

Behavior4/5

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

The annotations already establish that this is a read-only and open-world operation. The description adds useful behavioral context by noting that a tournament with no listed crew returns an empty list, and it describes the returned crew fields, though it does not discuss rate limits, authentication, or data freshness.

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 return contents and then immediately gives the prerequisite and empty-result behavior. It is compact, with no filler or redundant exposition.

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?

For a simple read-only tool with one parameter and an output schema, the description covers the essential purpose, required id source, returned entity types, and empty-result behavior. Its only notable gap is that it does not explicitly distinguish itself from the sibling participant/tournament tools.

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 description coverage is 100%, so the schema already documents tournament_id fully. The description repeats the numeric id and allowed source tools but adds no new syntax, format, or edge-case details beyond the schema, making the baseline 3 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?

The description uses a specific verb and resource: it returns casters, hosts, and analysts assigned to one GosuGamers esports tournament. The enumerated role types and returned fields make it clearly distinct from a general tournament lookup or a participant roster.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the required tournament_id and names the tools that can supply it, which gives clear prerequisite context. However, it does not explicitly say when to choose this over gosugamers_tournament, gosugamers_tournament_participants, or other tournament siblings, leaving the usage distinction implied.

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

All Crawlora MCP tools Inspect

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

Need Help?