Skip to main content
Glama
Sports Hub MCP Server

Sports Hub MCP Server

by danmorris27

opendota: Get heroes

opendota_get_heroes
Read-onlyIdempotent

Retrieve all Dota 2 heroes with IDs, names, primary attributes, and roles; optionally limit returned fields using a comma-separated list.

Instructions

List all Dota 2 heroes with id, name, primary attribute and roles.

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_heroes"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

A3.6/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 that the result is the full hero roster with specific attributes, but says nothing about pagination, caching, or the effect of the fields parameter.

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?

A single front-loaded sentence with no filler; the purpose and returned content are stated immediately and nothing is wasted.

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 usefully compensates by naming what each hero entry contains (id, name, primary attribute, roles). It is adequate for a simple read-only catalog tool, though it omits whether the full list is returned unpaginated and how the fields filter interacts with the default shape.

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% ('Keys to keep (comma-separated).'), so the single parameter is fully documented structurally. The description briefly enumerates available attributes (id, name, primary attribute, roles), which loosely maps to the fields keys but adds no real syntax or constraint detail, 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 ('List all Dota 2 heroes') and even names the returned attributes. It is clearly distinguishable from siblings like opendota_get_hero_stats or opendota_get_player_heroes by resource, though it does not explicitly call out that distinction.

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: an agent infers this is the tool for fetching a static hero catalog as opposed to per-player or per-match hero data. There is no explicit when-to-use statement, no exclusions, and no mention of the more specific opendota hero tools.

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