Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opendota_league_match_ids

Retrieve OpenDota match IDs for a single league, including amateur leagues omitted elsewhere, then use an ID with opendota_match for match details.

Instructions

OpenDota match IDs for one league. Returns match IDs for one league, including amateur leagues omitted from opendota_league_matches. An empty array is valid for a league with no matches. Copy an ID into opendota_match for match details.

Input Schema

NameRequiredDescriptionDefault
league_idYesPositive OpenDota league ID from opendota_leagues

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the return shape (bare match IDs), an important edge case ('An empty array is valid for a league with no matches'), and that details require a follow-up call rather than being included. Missing only access/rate-limit or ordering information.

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?

Four short sentences, front-loaded with the core purpose and with zero filler. Each sentence adds a distinct piece of information: scope, coverage gap, edge case, and next step.

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?

There is no output schema, and the description covers what matters: the return is a list of IDs, empty results are legitimate, and IDs feed opendota_match. Nothing an agent needs to call this correctly or interpret the result 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 description coverage is 100%, with league_id already documented as a positive OpenDota league ID sourced from opendota_leagues. The description adds only the 'for one league' scoping, which the schema already implies, so baseline 3 applies.

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 and resource ('Returns match IDs for one league') and immediately distinguishes itself from the sibling opendota_league_matches by noting it includes amateur leagues the sibling omits. An agent can tell exactly what this tool yields without opening the schema.

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?

Names the alternative it complements (opendota_league_matches) and the condition ('amateur leagues omitted'), plus the downstream call to make ('Copy an ID into opendota_match'). It stops short of an explicit 'use this instead of X when...' instruction, so it is clear but not fully prescriptive.

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