Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opendota_abilities

Retrieve and search Dota 2 ability reference data from OpenDota, returning compact summaries of behavior, targeting, damage, cooldown, mana cost, and descriptions by key or name.

Instructions

OpenDota Dota 2 ability reference. Returns Dota 2 abilities from OpenDota's constants table as compact summaries (key, display name, behavior, target team and type, damage type, dispellable, BKB pierce, cooldown, mana cost, innate flag, description), sorted by key. Internal helper entries without a display name are skipped. q searches the key and display name.

Input Schema

NameRequiredDescriptionDefault
qNoCase-insensitive search on the ability key or display name, for example blink
limitNoNumber of abilities to return, 1 to 500; defaults to 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it enumerates the returned fields (key, display name, behavior, target team/type, damage type, dispellable, BKB pierce, cooldown, mana cost, innate flag, description), states sorting by key, and discloses that entries without a display name are skipped. Missing only rate-limit or pagination behavior beyond `limit`.

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?

Front-loaded with the core purpose, then the returned fields, then the skip and search behaviors. It is dense but every clause adds value; no wasted sentences.

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 reference-list tool with only two fully documented params and no output schema, the field list, ordering, skip rule, and search behavior make it complete enough for an agent to call and interpret correctly.

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 both params are documented in the schema itself, so baseline is 3. The description only re-confirms that `q` searches key and display name and adds nothing for `limit` beyond the 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 (Returns) plus resource (Dota 2 abilities from OpenDota's constants table) and adds scope details: sorted by key, compact summaries, internal helper entries skipped. The purpose is unmistakable, though it doesn't explicitly distinguish itself from the sibling opendota_hero_abilities.

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 by calling it a 'reference' table and noting that `q` searches key and display name, but there is no explicit when-to-use / when-not guidance or naming of alternatives like opendota_hero_abilities or opendota_constants.

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