Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opendota_rank_distribution

Returns OpenDota Dota 2 rated-player counts and percentage shares across rank tiers, including medal, stars, cumulative totals, and sorted breakdowns for rank distribution analysis.

Instructions

OpenDota Dota 2 rank distribution. Returns how OpenDota's rated players are distributed over Dota 2 rank tiers: for each rank_tier (the first digit is the medal, the second the stars) the medal name, stars, player count, cumulative count and the share and cumulative share in percent, sorted by tier.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and does disclose the returned structure in detail: per-tier medal name, stars, player count, cumulative count, share and cumulative share, sorted by tier. It stops short of behavioral details such as data freshness, snapshot date, or whether counts are global only.

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?

Two sentences, zero waste, and the identifying statement is front-loaded before the field breakdown. Every clause either states purpose or specifies a returned value.

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 parameterless read endpoint with no annotations and no output schema, the description supplies both the purpose and a full enumeration of returned fields, which is everything an agent needs to decide to call it 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?

Zero parameters, so the baseline is 4. The description additionally explains the encoding of the returned `rank_tier` (first digit medal, second digit stars), which is useful semantics even though it refers to output rather than input.

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 resource (OpenDota's rated-player distribution across Dota 2 rank tiers) and implicitly the verb (returns). The purpose is unambiguous and unique among the opendota_* siblings, though it never explicitly distinguishes itself from them.

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?

Usage is only implied: the tool is parameterless, so the only guidance needed is 'call it to get the rank distribution', which the reader can infer. There is no statement of when this is preferable to siblings like opendota_benchmarks or opendota_hero_stats, and no exclusions.

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