Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opendota_items

Retrieve and filter Dota 2 item reference data from OpenDota constants as compact summaries, with search by key or display name and quality filters for item lookups.

Instructions

OpenDota Dota 2 item reference. Returns Dota 2 items from OpenDota's constants table as compact summaries (key, id, display name, quality, gold cost, behavior, cooldown, mana cost, components, active and passive abilities, numeric attributes), sorted by key. q searches the key and display name, quality filters by quality, and qualities lists the quality values present.

Input Schema

NameRequiredDescriptionDefault
qNoCase-insensitive search on the item key or display name, for example blink
limitNoNumber of items to return, 1 to 500; defaults to 50
qualityNoItem quality from the qualities list in the response; currently artifact, common, component, consumable, consumable;laning, epic, rare, secret_shop

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.7/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 reasonable work: it discloses the data source (OpenDota constants table), the compact shape of the returned summaries, and that results are sorted by key. It omits pagination/limit defaults and behavior on empty result sets, so it is not fully complete.

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?

Three tight sentences, front-loaded with what the tool returns, then the filters. The parenthetical field list is long but earns its place by describing the payload shape. No filler.

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?

No output schema exists, and the description compensates by enumerating the returned fields and sort order; the three parameters are fully covered by the schema. The dangling reference to `qualities` (a response facet, not a parameter) and the absence of limit behavior are the only gaps.

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%, so all three parameters are already documented (including examples for `q` and enum-like quality values). The description restates the `q` and `quality` semantics without adding syntax or edge-case detail, and never mentions `limit`. It also references a `qualities` parameter that is not in the schema, which is mildly confusing.

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 and resource: 'Returns Dota 2 items from OpenDota's constants table as compact summaries,' listing the fields and sort order. The 'constants table' framing implicitly separates it from per-hero item siblings like opendota_hero_items, but it never names an alternative explicitly.

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 description explains how to filter (`q` searches key and display name, `quality` filters by quality), which implies the retrieval use case, but gives no guidance on when to choose this over opendota_hero_items, opendota_constants, or opendota_abilities. There are no when-not conditions.

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