Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opendota_hero_matches

Fetch recent professional and public Dota 2 matches for a given hero ID, including side, result, KDA, duration, and league details; player account IDs are omitted.

Instructions

OpenDota Dota 2 recent matches of a hero. Returns recent professional and public matches in which a hero was played (about 100), each with the side it played, whether it won, its kills, deaths and assists, duration and league when there is one. Players' account ids are not returned. An unknown hero id returns not found.

Input Schema

NameRequiredDescriptionDefault
hero_idYesPositive hero ID from opendota-heroes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.8/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and mostly meets it: it discloses the fixed result size (~100), the per-record fields (side, win, KDA, duration, league), that player account ids are omitted, and that an unknown hero id yields not found. It omits ordering, date window, and any rate-limit or auth notes, but the behavioral picture is substantially richer than the bare schema.

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?

Three tight sentences, front-loaded with what the tool returns, then the field inventory, then the negative constraint and error case. Every clause carries information an agent would otherwise have to guess.

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 single-param read tool with no annotations or output schema, the essentials are present: record count, returned fields, exclusions, and error behavior. Minor gaps remain, such as result ordering or how 'recent' is bounded, but nothing critical is missing to invoke it correctly.

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?

With a single parameter at 100% schema coverage, the schema already documents hero_id as a positive ID from opendota-heroes. The description adds only the error behavior for invalid ids, which is useful but does not meaningfully deepen parameter semantics beyond the schema baseline.

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 verb and resource: recent matches of a Dota 2 hero, with a summary of fields returned. It is clearly distinct from siblings like opendota_hero_stats or opendota_hero_matchups by being match-level, though it never names an alternative explicitly.

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?

The description tells the agent what comes back (recent pro and public matches, ~100) and that account ids are excluded, which implies when to use it. But it gives no explicit when-to-use, when-not-to-use, or pointer to alternatives such as opendota_match for a single match or opendota_hero_stats for aggregates.

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