Skip to main content
Glama
Sports Hub MCP Server

Sports Hub MCP Server

by danmorris27

opendota: Get hero stats

opendota_get_hero_stats
Read-onlyIdempotent

Retrieve Dota 2 hero pick and win counts by bracket to assess current meta performance. Use it to compare hero stats for drafting or balance analysis.

Instructions

Get hero stats / current meta: per-bracket pick and win counts for every hero.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "opendota_get_hero_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, covering the safety profile. The description adds useful content scope ('per-bracket pick and win counts for every hero') but does not disclose return format, pagination, rate limits, or other behavioral traits beyond the annotations. With annotations carrying the main burden, a 3 is appropriate.

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?

One sentence, front-loaded with the purpose and then the specific return content. No filler, no redundancy, and the scope is immediately clear.

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?

Given no output schema and a single optional parameter, the description does a good job stating what data is returned ('per-bracket pick and win counts for every hero'). It omits details like default field behavior or return aggregation format, but those are minor for a simple read-only stats tool whose safety profile is already in annotations.

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%, and the single optional 'fields' parameter is documented by the schema itself. The description adds no parameter-level meaning beyond what the schema provides, so the baseline of 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 ('Get hero stats') and immediately clarifies scope with 'per-bracket pick and win counts for every hero', which distinguishes it from hero-list siblings like opendota_get_heroes. An agent can tell what data this returns without opening the schema.

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?

The phrase 'current meta' implies a usage context, but there is no explicit when-to-use guidance, no exclusions, and no mention of sibling alternatives such as opendota_get_heroes or opendota_get_player_heroes. The implied usage is clear enough to be minimally viable, but routing between similar tools is left to inference.

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