Skip to main content
Glama

get_pro_players

Retrieve professional Dota 2 player data to analyze competitive scene trends and identify top performers.

Instructions

Get list of professional players.

Args:
    limit: Number of players to retrieve (default: 10)

Returns:
    List of professional players

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The @mcp.tool() decorated handler function that implements the get_pro_players tool. It fetches professional players from the OpenDota API endpoint 'proPlayers', sorts them by team/name/account_id, limits the output, and formats a readable list of pro players with their team, country, and account ID.
    @mcp.tool()
    async def get_pro_players(limit: int = 10) -> str:
        """Get list of professional players.
    
        Args:
            limit: Number of players to retrieve (default: 10)
    
        Returns:
            List of professional players
        """
        if limit > 30:
            limit = 30  # Cap for reasonable response size
    
        pro_players = await make_opendota_request("proPlayers")
    
        if "error" in pro_players:
            return f"Error retrieving pro players: {pro_players['error']}"
    
        if not pro_players or not isinstance(pro_players, list) or len(pro_players) == 0:
            return "No professional players found."
    
        # Sort by name for consistency
        sorted_players = sorted(
            pro_players,
            key=lambda x: (
                x.get("team_name", ""),
                x.get("name", ""),
                x.get("account_id", 0),
            ),
        )
    
        formatted_players = []
    
        for i, player in enumerate(sorted_players[:limit]):
            account_id = player.get("account_id", "Unknown")
            name = player.get("name", "Anonymous")
            team_name = player.get("team_name", "No Team")
            country_code = player.get("country_code", "Unknown")
    
            formatted_players.append(
                f"{i+1}. {name}\n"
                f"   Team: {team_name}\n"
                f"   Country: {country_code}\n"
                f"   Account ID: {account_id}"
            )
    
        return "Professional Players:\n\n" + "\n\n".join(formatted_players)
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions a default limit and return type, but lacks details on permissions, rate limits, pagination, or data freshness. For a read operation with no annotation coverage, this is insufficient behavioral context.

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 well-structured and front-loaded, with a clear purpose statement followed by concise sections for arguments and returns. Every sentence adds value without redundancy, making it efficient and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (one optional parameter) and the presence of an output schema, the description is minimally adequate. However, without annotations and with siblings that overlap in domain, it lacks context on differentiation and behavioral traits, leaving gaps in completeness.

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?

The description adds meaningful semantics beyond the input schema: it explains that 'limit' is 'Number of players to retrieve' with a default of 10. With 0% schema description coverage and only one parameter, this effectively compensates, though it doesn't cover edge cases like maximum values.

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?

The description clearly states the tool's purpose: 'Get list of professional players.' It specifies the verb ('Get') and resource ('professional players'), making the intent unambiguous. However, it doesn't differentiate from sibling tools like 'get_player_by_id' or 'get_pro_matches', which prevents a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'get_player_by_id' for specific players and 'get_pro_matches' for matches, there's no indication of context, prerequisites, or exclusions, leaving usage unclear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/asusevski/opendota-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server