Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opendota_hero_items

Retrieve Dota 2 hero item purchase popularity by game phase, sorted by purchase count with item IDs resolved to internal names; use a hero ID to see what players buy over time.

Instructions

OpenDota Dota 2 hero item popularity. Returns the items players buy on a hero in four phases (start_game, early_game, mid_game, late_game), each sorted by purchase count, with item ids resolved to internal names such as power_treads through the item-id table. An unknown hero id returns not found.

Input Schema

NameRequiredDescriptionDefault
hero_idYesPositive hero ID from opendota-heroes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden well: it explains the four returned phases, sorting by purchase count, item-id-to-name resolution, and not-found behavior for unknown hero ids. It does not mention auth, rate limits, or read-only semantics, but the core behavior and error mode are disclosed.

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?

The description is compact and front-loaded, first naming the resource and then explaining the returned structure and edge case. Every sentence adds useful information with no repetition.

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 retrieval tool with no output schema, the description sufficiently explains the return shape: four phases, purchase-count ordering, and resolved item names. It also covers the failure case, so an agent has enough information to call and interpret the tool.

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?

The schema already has 100% description coverage for the single hero_id parameter, including the note that it should come from opendota-heroes. The description adds only the unknown-hero-id error behavior, so it does not meaningfully extend parameter semantics beyond the schema.

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 resource and scope: hero-specific item popularity, grouped into four game phases. This clearly distinguishes it from generic siblings like opendota_items or opendota_hero_stats.

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?

The intended use is implied by 'hero item popularity,' but the description does not explicitly say when to choose this over opendota_items, opendota_heroes, or other hero-scoped siblings. It also only indirectly points to opendota-heroes via the schema description for obtaining a valid hero ID.

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