Crawlora MCP

opendota_benchmarks

Read-only

Returns a Dota 2 hero's benchmark percentiles from OpenDota public games (optionally for role core or support, which changes the numbers a lot, and a rank bracket 1 Herald to 8 Immortal): ten per-minute metrics (gold_per_min, xp_per_min, kills_per_min, deaths_per_min, assists_per_min, last_hits_per_min, denies_per_min, hero_damage_per_min, hero_healing_per_min, tower_damage), each with values at percentiles 0.1 to 0.99. Provide hero_id from opendota_heroes; unknown ids return not found. Use it to judge how a hero's farm or damage compares with the field; use opendota_hero_stats for pick and win rates.

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": {
      "hero_id": "<hero_id>"
    },
    "name": "opendota_benchmarks"
  }
}

Input Schema

Name	Required	Description
`role`	No	Optional role of the games counted: core or support. Omit it for all roles.
`bracket`	No	Optional rank bracket 1 (Herald) to 8 (Immortal) to benchmark against; omit it for all ranks.
`hero_id`	Yes	Required positive hero ID from opendota_heroes.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 28, 2026

addedInput schema / properties / bracket

Added value: +{
+  "description": "Optional rank bracket 1 (Herald) to 8 (Immortal) to benchmark against; omit it for all ranks.",
+  "type": "integer"
+}

addedInput schema / properties / role

Added value: +{
+  "description": "Optional role of the games counted: core or support. Omit it for all roles.",
+  "type": "string"
+}

AddedOct 28, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare read-only and open-world behavior; the description adds the public-games source, notes that role changes the numbers a lot, specifies the percentile range 0.1 to 0.99, and discloses not-found behavior. It does not cover rate limits or auth, but with annotations that is a minor gap.

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?

The description is front-loaded and dense, but the opening sentence is long and the ten-metric list is substantial, partly duplicating the output schema. Still, each part provides relevant selection or invocation guidance.

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?

Given the output schema and annotations, the description covers the data source, parameters, return shape, error behavior, and sibling alternative. Nothing material is missing for an agent to call it correctly.

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%, so the baseline is 3; the description adds that role changes the numbers a lot, restates the bracket range, and warns that unknown hero IDs return not found. It adds useful context beyond the schema but not exhaustive 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?

States the specific verb and resource (returns Dota 2 hero benchmark percentiles) and names the source and scope. It explicitly distinguishes itself from opendota_hero_stats and points to opendota_heroes for the required ID.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use it to judge how a hero's farm or damage compares with the field, and names opendota_hero_stats for pick and win rates instead. It also gives the prerequisite for hero_id and notes unknown IDs return not found.

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

All Crawlora MCP tools Inspect

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

Need Help?