Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opendota_pro_players

Search and paginate a sanitized OpenDota professional player roster by team, player or team name, tag, or country code.

Instructions

OpenDota professional player roster. Returns a sanitized, searchable page of the OpenDota pro-player roster with player names, country codes and team tags. The upstream sends an unfiltered roster without pagination; this endpoint caches it and applies team_id, q, limit and offset locally. q searches names, tags and country codes. Account IDs, Steam IDs, profile URLs and avatars are omitted.

Input Schema

NameRequiredDescriptionDefault
qNoCase-insensitive substring in player/team names, team tags or country codes; maximum 200 characters
limitNoLocal page size, default 50, maximum 100
offsetNoZero-based local offset, default 0
team_idNoOptional positive team ID from opendota_teams

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.7/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 it does well: it discloses that the upstream is unfiltered/unpaginated, that filtering and paging happen locally/cached, and that account IDs, Steam IDs, profile URLs, and avatars are omitted from results. It omits auth/rate-limit/error behavior and result ordering, keeping it short of a 5.

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?

Front-loads the what and the output shape, then covers the caching/local-filtering quirk and omissions. Sentences are dense and mostly earn their place; the q/team_id explanation partly duplicates the schema but is defensible.

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?

With no output schema and no annotations, the description must supply return-value and behavioral context, which it largely does (fields returned, fields omitted, pagination behavior). Missing ordering and result-count/shape details keep it from a 5.

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%, so the schema already defines q, limit, offset, and team_id with defaults and maxima. The description adds only marginal meaning — that q matches names/tags/country codes and that team_id comes from opendota_teams — which mostly restates the schema. Baseline 3 is appropriate.

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?

Names the specific resource (OpenDota pro-player roster) and states the returned fields (names, country codes, team tags). It is distinct enough from opendota_team_players/opendota_teams through the local team_id/q filtering remark, though it never explicitly names a sibling to steer away from.

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 implied (searching/browsing the pro roster, optionally scoped by team_id from opendota_teams), but there is no explicit when-to-use or when-not, and no routing to opendota_team_players for a single team's roster. The reference to opendota_teams for team_id is a helpful hint, not guidance.

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