Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gosugamers_tournament_talents

Retrieve the casters, hosts and analysts assigned to a GosuGamers tournament by its numeric id, returning names, roles, language, country and profile links as JSON.

Instructions

GosuGamers tournament broadcast talents. Returns the casters, hosts and analysts assigned to one GosuGamers tournament: id, name, game, roles, broadcast language code, country, image and profile URL. An unknown tournament id, or a tournament with no listed crew, returns an empty list. Take the tournament id from gosugamers-tournaments, gosugamers-matches or gosugamers-results.

Input Schema

NameRequiredDescriptionDefault
tournament_idYesNumeric tournament id from gosugamers-tournaments, gosugamers-matches or gosugamers-results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.3/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 burden, and it does disclose the key edge case: an unknown tournament id or a tournament with no listed crew returns an empty list, which prevents the agent from misreading an empty result as a failure. It implies a pure read via 'Returns' but gives no info on auth, rate limits, or ordering of results.

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?

Three short sentences: identity, return shape, edge case, then id sourcing. The most decision-relevant content (what it returns and what counts as empty) is front-loaded with no 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?

There is no output schema, but the description compensates by enumerating the returned fields (id, name, game, roles, language code, country, image, profile URL). Combined with the empty-list semantics and id provenance, an agent has everything needed to call it correctly.

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 tournament_id parameter is already documented as a numeric id sourced from gosugamers-tournaments/matches/results. The description restates that same provenance without adding format details, so the schema does the heavy lifting — baseline 3 applies.

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 casters, hosts and analysts assigned to one GosuGamers tournament') and enumerates the returned fields. Naming broadcast crew roles implicitly separates it from gosugamers_tournament_participants (teams/players) and gosugamers_tournament (metadata), so an agent can pick the right sibling without opening schemas.

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 routes the agent to the upstream sources for the id ('Take the tournament id from gosugamers-tournaments, gosugamers-matches or gosugamers-results'), which is real usage guidance. It does not state a when-not case (e.g. use gosugamers_tournament_participants instead when you want teams or players), so it stops short of full alternative routing.

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