Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opendota_teams

Fetches paginated OpenDota team records—IDs, names, tags, rankings, and recent-match metadata—so you can browse teams and reuse IDs for team or match lookups.

Instructions

OpenDota team directory. Returns a zero-based page of OpenDota team records with team IDs, names, tags, ranking and recent-match metadata. OpenDota returns up to 1000 teams per page; use next_page while present. Use a team ID with opendota_team or opendota_team_matches.

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based page index; defaults to 0

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.9/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 behavioral burden and does add real context: the 1000-teams-per-page cap and the response-driven `next_page` loop tell the agent how to traverse the whole directory. It omits auth/rate-limit expectations and what an exhausted or out-of-range page returns, which are the remaining relevant behaviors for this read-only endpoint.

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?

Three front-loaded sentences with no filler: purpose and return fields first, pagination second, routing third. Minor ambiguity in that `next_page` is not an input parameter but a field of the response, which could momentarily confuse an agent reading the one-parameter schema.

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?

There is no output schema and no annotations, so the description must describe return content, which it does (team IDs, names, tags, ranking, recent-match metadata) alongside the pagination contract. For a one-parameter listing endpoint this is nearly complete; only the response envelope shape and pagination termination behavior remain unspecified.

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% and the single `page` parameter is already documented as a zero-based index defaulting to 0. The description's "zero-based page" phrasing restates the schema rather than adding new semantics, so baseline 3 applies — pagination mechanics come from the schema plus the `next_page` traversal hint, not from parameter detail.

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 specific resource (OpenDota team records) and states exactly what a call yields: a zero-based page of teams with IDs, names, tags, ranking and recent-match metadata. The final sentence routes to the sibling detail tools (opendota_team, opendota_team_matches), so an agent can distinguish this directory listing from those single-entity lookups without opening their schemas.

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?

It gives clear pagination procedure ("use `next_page` while present") and a downstream hand-off ("Use a team ID with opendota_team or opendota_team_matches"), but it never states when to choose this browse-all directory over another way of finding a team. Usage is implied by the enumeration framing rather than stated as an explicit trigger or exclusion.

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