Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opendota_constants

Decode Dota 2 match IDs by retrieving sorted OpenDota lookup tables for game modes, items, abilities, regions, patches, and related constants.

Instructions

OpenDota Dota 2 id lookup tables. Returns one OpenDota lookup table as a sorted list of id/name entries, used to decode ids in match data: game modes and lobby types (with balanced), patches (with release date), regions, server clusters (value is the region id), item and ability ids, permanent buff ids, experience thresholds per level (value) countries (id is the ISO code), order types (order_types, the unit order names) player slot colors (player_colors, hex colors), chat wheel phrases (chat_wheel, name is the label and text the message), item rarity colors (item_colors, text is the hex color), neutral ancient creeps (ancients) and skillshot abilities (skillshots). resource is one of game_mode, lobby_type, patch, region, cluster, item_ids, ability_ids, permanent_buffs, xp_level, countries.

Input Schema

NameRequiredDescriptionDefault
resourceYesLookup table; one of game_mode, lobby_type, patch, region, cluster, item_ids, ability_ids, permanent_buffs, xp_level, countries, order_types, player_colors, chat_wheel, item_colors, ancients, skillshots

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the return shape (sorted id/name list), that the output is a single table per call, and the extra fields each variant carries (`balanced`, `date`, `value`, ISO codes, hex colors). It does not explicitly say this is a read-only, unauthenticated, likely-cacheable lookup, which is the main remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with purpose and every clause carries information, but the body is one enormous run-on sentence of parenthetical annotations that is hard to scan. The content earns its place; the formatting does not.

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?

Single required enum parameter, no output schema, no annotations — the description compensates by enumerating each table and describing its row shape in detail. An agent has everything needed to pick a resource and interpret the result.

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 baseline is 3, but the description goes beyond the enum by explaining what each resource returns and how its `name`/`value`/`text`/`id` fields are repurposed per table — genuinely useful decoding guidance. Minor inconsistency: the closing sentence lists only 10 of the 16 enum values, omitting order_types, player_colors, chat_wheel, item_colors, ancients, and skillshots (though those are described earlier in prose).

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 one OpenDota lookup table as a sorted list of id/name entries' — and frames the reason ('used to decode ids in match data'). That framing cleanly separates it from the data-returning siblings like opendota_heroes, opendota_items, and opendota_match.

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?

The 'used to decode ids in match data' clause gives a clear reason to call it, i.e. whenever a raw id from match/hero/item data needs to be resolved to a readable name. It stops short of naming an alternative or exclusion (e.g. when to use opendota_items instead of resource=item_ids).

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