Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opendota_hero_abilities

Retrieve a Dota 2 hero's ability keys, eight talents by level, and facet details using a hero ID. Returns 404 when the hero ID is unknown or ability data is unavailable.

Instructions

OpenDota Dota 2 hero abilities, talents and facets. Returns a Dota 2 hero's ability keys, its eight talents by level and its facets (title, description, color, deprecated flag). An unknown hero id, or a hero OpenDota has no ability data for, returns 404.

Input Schema

NameRequiredDescriptionDefault
hero_idYesPositive hero ID from opendota-heroes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the exact shape of the response and states the failure semantics (404 for an unknown hero id or a hero with no ability data). It stops short of confirming read-only safety, but the retrieval framing makes that close to unambiguous.

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?

Two compact sentences with the payload described before the error case, so the reader gets the useful content first. The opening clause slightly restates the tool name, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter lookup with no output schema, the description covers what is returned, the fields within facets, and the failure mode, which is everything an agent needs to call it and interpret the result.

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 coverage is 100% and the schema already says 'Positive hero ID from opendota-heroes'. The description adds only the negative case (invalid id yields 404), so it neither compensates for nor exceeds the schema. Baseline 3 is appropriate.

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?

The description names a specific resource and enumerates the payload: ability keys, eight talents by level, and facets with their fields. It is clearly a per-hero lookup, which separates it from the global opendota_abilities sibling, though it never names that sibling explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of the alternative opendota_abilities or opendota_hero_descriptions tools. The only operational hint is embedded in the schema (hero_id from opendota-heroes), not in the description itself.

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