Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opendota_leagues

Retrieve every OpenDota league ID with its source name, ticket, banner, and tier; filter by tier, including unrated, to select leagues for match lookups.

Instructions

OpenDota league directory. Returns every league ID and its source name, ticket, banner and tier. The source list is large and can include historical or excluded leagues. Filter tier locally; unrated selects source rows whose tier is blank. The response echoes tier_filter. Use a returned ID with opendota_league_matches.

Input Schema

NameRequiredDescriptionDefault
tierNoOptional exact source tier filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description does real work: it warns the source list is large and includes historical/excluded leagues, and notes the response echoes tier_filter. It is silent on pagination or size limits and on any auth/rate-limit behavior, so the behavioral picture is only partly filled in.

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?

Five short sentences, each carrying a distinct fact (purpose, return shape, list caveat, filter semantics, handoff). Front-loaded with the resource and none of it is filler.

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?

No output schema exists, so the description correctly takes on the return-value burden by naming the echoed fields, and the tier_filter echo is disclosed. It stops short of saying whether results are bounded or paginated for a directory it itself calls large.

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% with an enum, so the baseline is 3, but the description adds genuine meaning beyond the schema: `unrated` is defined as blank-tier source rows, and the filtering is described as local rather than server-side.

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?

Opens with a concrete verb+resource ('OpenDota league directory') and enumerates the returned fields (ID, source name, ticket, banner, tier). This clearly separates it from siblings like opendota_league (single item) and opendota_league_matches, which the description explicitly hands off to.

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?

States the practical usage pattern: filter `tier` locally, `unrated` selects blank-tier rows, and feed a returned ID into opendota_league_matches. It does not explicitly contrast with opendota_league or opendota_league_match_ids, so routing is implied rather than fully enumerated.

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