Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

opendota_team_heroes

Read-only

Returns a Dota 2 team's hero pool: each hero played with games, wins and win rate, sorted by games played. Provide team_id from opendota_teams. Unknown teams return not found. Use opendota_team_matches for the underlying games.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "team_id": "<team_id>"
    },
    "name": "opendota_team_heroes"
  }
}

Input Schema

NameRequiredDescriptionDefault
team_idYesRequired positive OpenDota team ID from opendota_teams or a match response.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover readOnlyHint and openWorldHint, so the description doesn't need to restate safety. It adds real behavioral context: the sort order, the exact metrics returned, and the not-found behavior for unknown teams.

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?

Four short sentences, front-loaded with the operation and output shape, then provenance, error behavior, and the sibling alternative. Slightly redundant since the team_id provenance repeats the schema description.

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 single-parameter read tool with an output schema and clear annotations, nothing an agent needs is missing: output shape, sorting, ID provenance, and error case are all covered.

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 team_id property already documents that it is a required positive OpenDota team ID. The description's 'Provide team_id from opendota_teams' adds only marginal provenance beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('Returns a Dota 2 team's hero pool') and immediately disambiguates the scope: per-hero aggregates (games, wins, win rate) sorted by games played. That clearly separates it from opendota_team_matches, which returns the underlying games.

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?

Explicitly tells the agent where team_id comes from (opendota_teams) and names opendota_team_matches as the alternative for raw game data. It lacks an explicit 'when not to use' statement, but the routing is clear enough to pick correctly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources