Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

opendota_constants

Read-only

Returns one OpenDota Dota 2 lookup table as sorted id/name entries to decode ids in match data: game_mode and lobby_type (with balanced flag), patch (with release date), region, cluster (value is region id), item_ids, ability_ids, permanent_buffs, xp_level (value is experience threshold) countries, order_types (unit order names), player_colors (slot hex colors), chat_wheel (phrases; name is the label, text the message), item_colors (rarity hex colors in text), ancients (neutral ancient creep names) or skillshots (skillshot ability names). Provide resource. Use opendota_heroes for hero ids.

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": {
      "resource": "<resource>"
    },
    "name": "opendota_constants"
  }
}

Input Schema

NameRequiredDescriptionDefault
resourceYesRequired lookup table: 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 or skillshots.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / resource / description
      Previous value: -"Required lookup table: game_mode, lobby_type, patch, region, cluster, item_ids, ability_ids, permanent_buffs, xp_level, countries, order_types or player_colors."New value: +"Required lookup table: 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 or skillshots."
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety and freshness are covered. The description adds real behavioral detail beyond that: entries are sorted id/name pairs, and specific tables carry extra fields (lobby_type has a balanced flag, patch has a release date, chat_wheel has label/message). It doesn't mention caching, rate limits, or table stability, which keeps it below a 5.

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?

Purpose is front-loaded in the first clause and there is no filler, but the resource catalogue is a single very long sentence with 17 comma-separated items, which makes it harder to scan than a short list. Every element does earn its place content-wise.

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 one-parameter lookup tool with an output schema, the description covers the operation, the input space, the entry shape (sorted id/name), and the sibling to use instead for hero ids. Return-value detail is correctly deferred to the output schema.

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 the baseline is 3, but the description goes past the schema's bare enum list by explaining what the name/value means per table (cluster value is a region id, xp_level value is an experience threshold, player_colors are slot hex colors, item_colors are rarity hex colors). A few resources (region, countries, item_ids, permanent_buffs) are named without that semantic gloss.

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?

The description opens with a specific verb and resource — 'Returns one OpenDota Dota 2 lookup table as sorted id/name entries to decode ids in match data' — which states both the operation and the intended downstream use. It also explicitly names the sibling opendota_heroes for hero ids, so an agent can route between them without opening a schema.

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?

Usage is anchored by 'to decode ids in match data', and the final sentence routes hero id lookups to opendota_heroes, an explicit alternative. There is no exclusion or guidance for other id-decoding siblings (items, abilities are in the resource list but not cross-referenced), so it stops short of full when/when-not coverage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
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