Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opendota_public_matches

Retrieve recent public Dota 2 ranked matches by average rank tier, including heroes, game mode, lobby type, and pagination.

Instructions

OpenDota Dota 2 recent public matches by rank. Returns about 100 recent ranked public Dota 2 matches with the heroes on each side, game mode, lobby type and average rank tier, optionally limited to a rank range. Rank tiers are the medal (1 Herald, 2 Guardian, 3 Crusader, 4 Archon, 5 Legend, 6 Ancient, 7 Divine, 8 Immortal) times ten plus stars 1 to 5. Page back with less_than_match_id set to the previous next_less_than_match_id. Players' account ids are not returned.

Input Schema

NameRequiredDescriptionDefault
max_rankNoHighest average rank tier, same form as min_rank; not below min_rank
min_rankNoLowest average rank tier, medal 1-8 times ten plus stars 1-5
less_than_match_idNoReturn matches older than this match id

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 disclosure burden and does well: it states the approximate result size (~100 matches), lists key returned fields, explains pagination, and notes that players' account ids are omitted. It does not mention authentication or rate limits, which keeps it from 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.

Conciseness5/5

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

The description is front-loaded with the core purpose and then supplies only necessary details: result contents, rank encoding, pagination, and the account-id exclusion. Every sentence contributes useful selection or invocation information.

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?

There is no output schema, so the description needs to explain return values; it does so by naming the main fields and the approximate result count. It is nearly complete, though it leaves 'recent' undefined and does not mention rate limits or authentication.

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 schema already documents all three parameters. The description still adds value by explaining the rank-tier encoding and, more importantly, describing how to page using less_than_match_id with the previous next_less_than_match_id.

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?

The description clearly states a specific resource and scope: recent ranked public Dota 2 matches, optionally filtered by rank. It implicitly distinguishes itself from pro-match and hero-match siblings by emphasizing public ranked matches, but it does not explicitly name an alternative tool.

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?

It gives clear usage context: fetch recent public ranked matches, optionally constrained with min_rank/max_rank, and page backward using less_than_match_id. It does not explicitly say when to choose it over siblings such as opendota_find_matches or opendota_pro_matches, but the context is sufficient for selection.

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