Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opendota_records

Get top 100 single-match Dota 2 records for a specified stat (kills, deaths, etc.) with rank, match id, hero, and value; use returned match id with opendota-match.

Instructions

OpenDota Dota 2 single-match record leaderboards. Returns the top 100 single-match records for one stat (kills, deaths, assists, last_hits, denies, gold_per_min, xp_per_min, hero_damage, tower_damage, hero_healing, duration): rank, match id, start time, hero (with name) and the record value. Use opendota-match with a returned match id.

Input Schema

NameRequiredDescriptionDefault
fieldYesRecord field; one of kills, deaths, assists, last_hits, denies, gold_per_min, xp_per_min, hero_damage, tower_damage, hero_healing, duration

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?

No annotations are provided, so the description must carry behavioral load; it discloses the top-100 limit, the one-stat scope, the returned fields, and the follow-up match lookup. It still omits data freshness/all-time scope and rate-limit/auth details, but the core read behavior is clear.

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 and compact: purpose, return shape, and follow-up are delivered in three sentences with no filler. The enum list is lengthy but directly relevant to invocation and does not obscure the main point.

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?

For a one-parameter read endpoint with no output schema, the description gives enough to call it correctly: what it returns, how many records, which stat, and what to do with a match id. It could add data-scope/freshness context, but no major calling information is missing.

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% and the single `field` parameter is a fully enumerated enum; the description repeats the enum list and says 'one stat' but adds little semantic detail beyond the schema (e.g., no explanation of sorting or record meaning). Baseline 3 applies because the schema already documents the parameter.

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 uses a specific verb ('Returns') and resource ('top 100 single-match records for one stat'), naming the stat domain and returned fields. It also distinguishes the tool from match-detail lookup by pointing to opendota-match for a returned match id.

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?

It gives a useful follow-up ('Use opendota-match with a returned match id') but does not explicitly state when to choose opendota_records over other OpenDota leaderboard/stat tools or when not to use it. The single-match leaderboard phrase implies usage, but alternatives/exclusions are absent.

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