Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opendota_match

Fetch a compact parsed Dota 2 match summary and player lines using a numeric OpenDota match ID to inspect match details and performance.

Instructions

OpenDota match detail. Returns a compact parsed match summary and player lines for one numeric OpenDota match ID. Copy the ID from opendota_live, opendota_pro_matches, opendota_league_matches, or opendota_league_match_ids. Replay-derived player data can be absent or delayed; a missing match ID returns not found. Steam account IDs, chat logs, replay salts and raw telemetry are not returned. hero_id is resolved with opendota_heroes.

Input Schema

NameRequiredDescriptionDefault
idYesPositive OpenDota match ID from live, pro-match, league-match, or league-match-ID results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that replay-derived player data may be absent or delayed, that a missing ID returns not found, and enumerates what is not returned (Steam account IDs, chat logs, replay salts, raw telemetry). It does not explicitly state read-only/no-auth behavior, but the 'returns' framing implies a read.

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?

The purpose and return shape are front-loaded in the first sentence, followed by sourcing, caveats, and exclusions. It is compact and every sentence carries distinct information, though the exclusion list is slightly dense.

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 description summarizes the return (compact parsed summary and player lines) and covers availability/error caveats and negative space. It stops short of detailing the exact fields in the summary, but provides enough for correct invocation.

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% and already documents the `id` parameter. The description adds value beyond the schema by specifying it is 'one numeric OpenDota match ID' and enumerating the source endpoints to copy it from, reinforcing the positive-integer constraint.

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?

States a specific verb+resource+scope: 'OpenDota match detail' returning 'a compact parsed match summary and player lines' for one numeric match ID. This clearly distinguishes it from sibling list tools like opendota_live, opendota_pro_matches, and opendota_find_matches.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent where to obtain the required ID: 'Copy the ID from opendota_live, opendota_pro_matches, opendota_league_matches, or opendota_league_match_ids.' This names the alternatives and the condition that selects this detail tool over those list tools.

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