Skip to main content
Glama
Sign In

Opendota

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Hero Stats

hero_stats
Read-onlyIdempotent

Dota 2 hero meta: per-hero pick/win/ban counts in pro play, primary attribute, attack type, and roles. Optionally filter by role (e.g. "Carry", "Support"). OpenDota keyless data.

Input Schema

NameRequiredDescriptionDefault
roleNoOptional role filter, e.g. "Carry", "Support", "Initiator".
limitNoMax heroes to return (default 30).
_apiKeyNoOptional — your own OpenDota API key (free, from https://www.opendota.com/api-keys) for higher, PER-KEY rate limits. The endpoint is keyless: omit this and calls still work, but OpenDota rate-limits by calling IP and the shared Worker egress IP is frequently already at quota from unrelated traffic — a caller-supplied key escapes that.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / _apiKey
      Added value: +{
+  "description": "Optional — your own OpenDota API key (free, from https://www.opendota.com/api-keys) for higher, PER-KEY rate limits. The endpoint is keyless: omit this and calls still work, but OpenDota rate-limits by calling IP and the shared Worker egress IP is frequently already at quota from unrelated traffic — a caller-supplied key escapes that.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 10,
+    "role": "Carry"
+  },
+  {
+    "limit": 30
+  }
+]
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint, destructiveHint=false), so the bar is lower. The description adds that this is keyless OpenDota data, hinting at an external source, but doesn't surface the IP-based rate-limit caveat directly — that lives in the _apiKey schema text.

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?

Three compact sentences, front-loaded with what the tool returns, then the optional filter, then the data source. Minimal waste, though the trailing source note could be folded in rather than standing alone.

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?

No output schema exists, so the description usefully enumerates the returned fields (pick/win/ban counts, attribute, attack type, roles), which is the key missing piece an agent would otherwise lack. Rate-limit behavior is covered by the schema's _apiKey description.

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%, so role and limit are already documented in the schema; baseline 3 applies. The description's role examples ("Carry", "Support") marginally reinforce the schema but add no new syntax or format detail beyond it.

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 resource (Dota 2 hero meta) and enumerates the returned fields — pick/win/ban counts, primary attribute, attack type, roles. An agent can tell this apart from get_player or pro_matches by the per-hero meta focus, though no sibling is named explicitly.

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 only usage instruction is that the role filter is optional, with examples. There is no guidance on when to prefer this over adjacent Dota tools (get_player, pro_matches) and no when-not conditions, so usage is implied rather than stated.

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

All Opendota toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources