Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opendota_heroes

Resolve OpenDota hero_id values to hero names, primary attributes, and attack types so match data can be interpreted accurately.

Instructions

OpenDota hero directory. Returns the live OpenDota hero lookup needed to resolve hero_id values in live and detailed match responses. It includes every current hero ID with its internal name, localized name, primary attribute (agi, all, int, or str) and attack type (Melee or Ranged).

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that this is a 'live' OpenDota lookup and enumerates the returned fields, which establishes it as a read-only static directory, but says nothing about caching, rate limits, or whether the response is keyed by hero_id or an array.

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 sentences, front-loaded with the identity of the resource before the detail, with no filler. Minor redundancy in 'live OpenDota hero lookup' echoing 'OpenDota hero directory', but nothing that wastes the reader's attention.

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 parameters, no annotations, and no output schema, the description does most of the necessary work by naming the fields returned and the reason to call it. The residual gap is response packaging (array vs keyed object) and whether the data is static across patches.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, so the baseline is 4. The description goes slightly beyond by describing the shape of each entry (ID, internal name, localized name, attribute enum, attack type), which usefully pre-signals the return contract in the absence of an output schema.

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+resource ('OpenDota hero directory') and describes exactly what it returns: hero ID, internal name, localized name, primary attribute, and attack type. The 'resolve hero_id values in match responses' framing carves out a role distinct from siblings like opendota_hero_stats or opendota_hero_abilities, 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?

Usage is implied rather than stated: it is the lookup you need when a match response contains an unresolved hero_id. There is no explicit when-to-use/when-not statement and no routing to alternatives such as opendota_constants or opendota_hero_stats, so the agent must infer selection.

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