Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opendota_team_players

Retrieve a Dota 2 team's player history by team ID, including games played, wins, and current membership status, with current members listed first.

Instructions

OpenDota Dota 2 team player history. Returns the players who have played for a team with games played, wins and whether they are a current member, current members first. Steam account ids are not returned. An unknown team id returns not found.

Input Schema

NameRequiredDescriptionDefault
team_idYesPositive OpenDota team ID from opendota-teams or a match response

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 provided, the description carries the behavioral burden and does so reasonably well: it discloses that current members are ordered first, that Steam account IDs are omitted, and that an unknown team ID returns not found. It does not mention auth, rate limits, or pagination, but for a read-only lookup tool it adds useful behavioral context beyond the schema.

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 three compact sentences, front-loaded with the purpose and then the key return and error behavior. Every sentence adds useful information without repetition.

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, so the description must explain return values, and it does: players, games played, wins, current-member status, ordering, omitted Steam IDs, and not-found behavior. Given the simple one-parameter read-only nature of the tool, no important missing context is apparent.

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?

There is only one parameter, team_id, and the schema description coverage is 100%, so the schema already explains that it is a positive OpenDota team ID from opendota-teams or a match response. The tool description adds only the error behavior for an unknown team ID, not additional parameter semantics.

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 states a specific resource and scope: Dota 2 team player history. It clearly says it returns players who have played for a team, including games, wins, and current membership, which distinguishes it from sibling team tools like opendota_team and opendota_team_matches.

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?

The use case is implied by 'team player history,' but the description does not explicitly say when to use this tool versus alternatives such as opendota_team_heroes, opendota_team_matches, or opendota_teams. No exclusions or routing guidance are provided.

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