Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opendota_hero_durations

Retrieve a Dota 2 hero's games and wins grouped into five-minute game-length bins to show whether the hero is stronger early or late; unknown hero IDs return not found.

Instructions

OpenDota Dota 2 hero win rate by game duration. Returns a hero's games and wins grouped by game length in five-minute bins (start_minute is the bin's first minute), sorted by length, to show whether the hero is stronger early or late. An unknown hero id returns not found.

Input Schema

NameRequiredDescriptionDefault
hero_idYesPositive hero ID from opendota-heroes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it discloses the aggregation shape (games and wins), the binning scheme and the meaning of `start_minute`, the sort order, and the not-found behavior for an unknown hero id. It leaves out only secondary operational detail such as rate limits or whether results are cached/fresh.

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?

Three tight sentences, front-loaded with what the tool returns, then how the data is binned and sorted, then the error case. No filler or restatement of the tool name.

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?

For a single-parameter read tool with no output schema, the description covers the essentials: return fields, bin granularity, ordering, and failure behavior. A slightly fuller sketch of the response (e.g. whether a computed win rate is included alongside games and wins) would close the remaining gap.

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 schema already says the param is a positive hero ID from opendota-heroes, so baseline is 3. The description adds only one param-relevant fact — that an unknown hero id returns not found — but no format, range, or lookup guidance beyond the schema.

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: returns a hero's games and wins grouped by game length in five-minute bins, sorted by duration. The scoping is precise enough to distinguish it from sibling stats tools like opendota_hero_stats or opendota_hero_matchups without opening a schema.

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

Usage Guidelines4/5

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

It gives a clear use case — 'to show whether the hero is stronger early or late' — which tells an agent when this tool is the right choice. It does not name exclusions or point to alternative sibling tools for related hero-stat questions, so it stops short of full routing guidance.

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