Skip to main content
Glama
Sports Hub MCP Server

Sports Hub MCP Server

by danmorris27

opendota: Get player heroes

opendota_get_player_heroes
Read-onlyIdempotent

Retrieve a player's per-hero Dota 2 stats, including games, win rate, and last played, from a Steam32 account ID to analyze hero performance.

Instructions

Get a player's per-hero stats (games, win rate, last played).

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": {
      "account_id": "<account_id>"
    },
    "name": "opendota_get_player_heroes"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).
account_idYesSteam32 account id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds the returned data shape, but says nothing about OpenDota API-key/auth requirements, rate limits, or how many heroes are returned. With annotations carrying the safety burden, this is a reasonable 3.

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?

One sentence, zero filler, front-loaded with the verb and resource. It is efficient, though the extreme brevity is part of why usage and behavior context are thin.

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, the description helpfully enumerates the returned fields (games, win rate, last played), which is exactly what an agent needs for a simple read-only lookup. It could still mention auth or result ordering, but it is largely complete for a two-parameter read tool.

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%: account_id ('Steam32 account id') and fields ('Keys to keep, comma-separated') are both documented in the schema. The description adds no parameter-level detail beyond that (e.g., what keys 'fields' accepts), so the baseline 3 applies.

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?

States a specific verb and resource ('Get a player's per-hero stats') and even names the payload ('games, win rate, last played'), which distinguishes it from siblings like opendota_get_player_matches and opendota_get_player_win_loss. It never explicitly names those alternatives, so it stops short of full sibling differentiation.

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?

No when-to-use guidance, no prerequisites, and no routing to the obvious alternatives (get_player_win_loss for aggregate W/L, get_player_matches for match history). The usage context is only implied by the tool name.

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