Crawlora MCP

opendota_hero_descriptions

Read-only

Returns what Aghanim's Scepter and Aghanim's Shard do for every Dota 2 hero or for one hero_id (from opendota_heroes): whether each upgrade exists, its description, the skill it changes and whether it adds a new skill. include_lore=true also returns each hero's lore text (about 155 KB for all heroes), so leave it off unless you need the story. An unknown hero_id returns not found.

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_hero_descriptions"
  }
}

Input Schema

Name	Required	Description	Default
`hero_id`	No	Optional positive hero ID from opendota_heroes; omit it for all 127 heroes.
`include_lore`	No	Optional; true adds each hero's lore text (about 155 KB for all heroes). Default false.

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

Behavior4/5

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

Annotations already cover read-only/open-world safety, and the description adds real behavioral detail beyond them: the ~155 KB payload cost of include_lore, the false default, and that an unknown hero_id yields not found rather than an error or empty list. Auth/rate-limit behavior is unstated, keeping it at 4.

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?

Front-loads what is returned, then handles the two parameters and the not-found edge case in two dense but waste-free sentences. No filler or restatement of the name.

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?

An output schema exists, so return shape needs no explanation, yet the description still previews the fields. Combined with the size warning, default values, and not-found behavior, an agent has everything needed to call this correctly.

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%, so both parameters are already documented; the description still adds value by tying hero_id to its source tool and the 'all 127 heroes' default, and by framing include_lore as a size tradeoff rather than just a boolean.

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 — returns Aghanim's Scepter/Shard upgrade data for every Dota 2 hero or one hero_id — and enumerates the returned fields (existence, description, changed skill, new-skill flag). This clearly separates it from opendota_heroes (id lookup) and opendota_hero_abilities (ability data).

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

Usage Guidelines4/5

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

Gives clear operating context: hero_id is optional, omit it for all heroes, hero_id comes from opendota_heroes, and include_lore should be left off unless the story is needed. It stops short of explicitly contrasting with the closest sibling (opendota_hero_abilities), so not a 5.

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?