Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gosugamers_team

Fetches a GosuGamers esports team profile including Elo rating, world and regional ranking, win/loss record, win rate, earnings, roster with join dates, and upcoming matches for the specified game and team ID.

Instructions

GosuGamers esports team profile. Returns one GosuGamers team: name, tag, country, logo, GosuGamers Elo rating and world and regional ranking, win/loss/draw record and win rate, current streak, career earnings in USD, social links, the roster with join dates and the team's next upcoming matches. A team of a different game than game returns not found.

Input Schema

NameRequiredDescriptionDefault
gameYesGame section; one of dota2, counterstrike, lol, valorant, mobile-legends, pubg-mobile, wild-rift, free-fire, battlegrounds-mobile-india
team_idYesNumeric team id from gosugamers-matches, gosugamers-results or gosugamers-match (teams[].id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.8/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden; it discloses the key failure mode ('a team of a different game than game returns not found') and the complete returned payload, which substitutes for a missing output schema. It does not mention auth, rate limits, or whether the upcoming-matches list is bounded, so a 4 rather than a 5.

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?

The identity statement is front-loaded and the failure condition is placed last where it belongs. The middle sentence is a long comma-chained field list, which is dense but each item is a distinct returned value rather than filler.

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?

With no output schema and no annotations, the field enumeration is what tells the agent what it will get back, and the game-mismatch note covers the main error path. Missing only secondary operational details like pagination of upcoming matches or rate behavior.

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 both parameters are already documented, but the description adds real meaning beyond the schema: the `game` parameter must match the team's game or the lookup fails. That interaction between two parameters is not derivable from the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

It states a specific verb and resource ('Returns one GosuGamers team') and enumerates the profile payload (Elo, rankings, record, roster, upcoming matches). It does not name the nearby sibling gosugamers_team_results, so an agent must infer the boundary between a profile lookup and a results lookup.

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?

Usage is only implied: needing a team_id (documented in the schema, not the description) and the note that a mismatched `game` yields not-found signal a lookup-by-id pattern. There is no explicit 'use this instead of gosugamers_team_results when...' steering, which matters given the very large sibling set.

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