Crawlora MCP

opendota_hero_abilities

Read-only

Returns a Dota 2 hero's ability keys, talents by level (key and level) and facets (title, description, color, deprecated flag). Provide hero_id from opendota_heroes; unknown ids return not found. Use it for a hero's kit and talent tree; look up an ability or talent key with opendota_abilities.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "hero_id": "<hero_id>"
    },
    "name": "opendota_hero_abilities"
  }
}

Input Schema

Name	Required	Description	Default
`hero_id`	Yes	Required positive hero ID from opendota_heroes.

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.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's added value is the failure mode: "unknown ids return not found." That is real behavioral disclosure an agent can plan around. It stops short of describing rate limits or pagination, but with a single-item lookup tool that is minor.

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 sentences, all load-bearing: payload contents first, parameter provenance second, sibling routing last. No restatement of the tool name and no filler.

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?

One required parameter, 100% schema coverage, and an output schema that already documents the return shape, so the description need not restate fields. Everything an agent needs to call it correctly and know what happens on a bad ID is present.

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?

Schema coverage is 100% and the only parameter is documented there, so the baseline is limited. The description still adds meaning by tying hero_id to its authoritative source (opendota_heroes) and stating the consequence of an invalid value, which the schema does not.

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?

Names a specific verb and resource ("Returns a Dota 2 hero's ability keys, talents by level... and facets") and enumerates exactly what the payload contains. An agent can distinguish it from opendota_abilities or opendota_heroes without opening any schema.

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?

Explicitly states the retrieval context ("Use it for a hero's kit and talent tree") and routes the agent to the sibling ("look up an ability or talent key with opendota_abilities"). It also says where hero_id must come from (opendota_heroes), closing the usual lookup-origin gap.

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.

Resources

Need Help?