Crawlora MCP

opendota_abilities

Read-only

Searches the Dota 2 ability table and returns compact summaries: key, display name, behavior, target team and type, damage type, dispellable, BKB pierce, cooldown and mana cost per level, innate flag and description. Provide q (key or name search) and limit (default 50). Use it to look up what an ability does; use opendota_hero_abilities to see which abilities, talents and facets one hero has.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "opendota_abilities"
  }
}

Input Schema

Name	Required	Description	Default
`q`	No	Optional case-insensitive search on the ability key or display name, for example blink.
`limit`	No	Optional number of abilities to return, 1 to 500; defaults to 50.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover read-only and open-world safety, but the description adds value by disclosing the exact shape of results (per-level cooldown/mana, BKB pierce, dispellable, innate flag) and the default result cap. It does not discuss confidence in matching or behavior when q is empty, which is the only notable gap.

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 sentences, front-loaded with purpose, then usage and alternative. The field enumeration is long but earns its place for selection; a slight trim would improve it.

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?

An output schema exists, so listing return fields is largely redundant, but the description still covers purpose, scope, defaults, and sibling routing adequately for a two-optional-param read-only search tool. Nothing an agent needs to call it is missing.

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?

With 100% schema description coverage, the schema already documents both q and limit in detail, including the 1-500 range and default. The description restates q as 'key or name search' and limit's default of 50 without adding new syntax or constraints.

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 ('Searches the Dota 2 ability table') and enumerates the returned fields, so the agent knows exactly what data comes back. It explicitly names the sibling opendota_hero_abilities and contrasts the two scopes, making disambiguation immediate.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use ('look up what an ability does') paired with the alternative and its condition ('use opendota_hero_abilities to see which abilities, talents and facets one hero has'). No inference is required to route between the two tools.

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

All Crawlora MCP tools Inspect

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.