Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opendota_league

Retrieve Dota 2 league details and participating teams by OpenDota league ID, including name, tier, ticket, banner, team ratings, and records.

Instructions

OpenDota Dota 2 league detail and teams. Returns one league's name, tier (amateur, excluded, premium, professional or unrated when blank), ticket and banner, plus the teams that played in it with rating and record. An unknown league id returns not found.

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.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 behavioral burden. It discloses that this is a retrieval returning specific league fields and teams, and it states the unknown-id behavior, though it does not mention auth requirements, rate limits, or whether any nested team data is paginated.

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, compact, and every sentence adds useful information: what is returned, the tier enum values, and the not-found behavior. There is no filler.

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?

For a simple one-parameter detail endpoint with no output schema, the description explains the return contents, tier values, and error behavior. That is sufficient for an agent to call it correctly without additional documentation.

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 league_id parameter is already documented in the schema as a positive OpenDota league ID from opendota-leagues. The description adds no additional parameter semantics beyond the schema.

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 names the resource and scope precisely: one Dota 2 league's details plus its teams. It is clearly distinct from the plural opendota_leagues list and from match-focused siblings by saying it returns one league's metadata and participating teams.

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?

Usage is only implied by the detail scope and the required league_id. The description does not explicitly say when to use this instead of opendota_leagues, opendota_league_matches, or opendota_teams, nor does it name alternatives.

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