Crawlora MCP

opendota_scenarios

Read-only

Returns OpenDota Dota 2 scenario datasets as games, wins and win rate rows, most games first. Provide kind: item-timings (hero buys an item by a time; filter hero_id and item), lane-roles (hero in lane_role 1 to 4 at a time; filter hero_id and lane_role) or misc (courier_kill, first_blood, neg_chat_1min, pos_chat_1min by side and region; filter scenario). Filters that do not match the kind are rejected; limit caps rows. Use it to see which item timings win; use opendota_hero_items for plain purchase counts.

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": {
      "kind": "<kind>"
    },
    "name": "opendota_scenarios"
  }
}

Input Schema

Name	Required	Description
`item`	No	Optional item name from opendota_constants item_ids, for example bfury; item-timings only.
`kind`	Yes	Required dataset: item-timings, lane-roles or misc.
`limit`	No	Optional number of rows to return, 1 to 2000, most games first; defaults to all.
`hero_id`	No	Optional positive hero ID from opendota_heroes; item-timings and lane-roles only.
`scenario`	No	Optional scenario: courier_kill, first_blood, neg_chat_1min or pos_chat_1min; misc only.
`lane_role`	No	Optional lane role 1 to 4 (1 safe lane, 2 mid, 3 off lane, 4 jungle); lane-roles only.

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.

AddedOct 28, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's added value is ordering (most games first), the hard rejection of non-matching filters, and the limit cap. These are real behavioral facts an agent could not infer from the annotations, though it does not mention data recency or any rate limits.

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?

A single front-loaded paragraph with no filler; the kind enumeration and the sibling pointer come early. The dense parentheticals make it slightly run-on, but nearly every clause carries operational information.

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?

With an output schema present, the description does not need to explain return values, yet it still summarizes the row shape. For a read-only, six-parameter tool with one required argument, nothing an agent needs in order to call it correctly is missing.

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%, so the per-parameter meaning (hero_id, item, lane_role, scenario, limit) is already structured data and the description largely restates it. It adds only marginal value, notably that misc scenarios are broken out 'by side and region', which the schema does not say.

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 gives a specific verb and resource (returns OpenDota Dota 2 scenario datasets) plus the exact row shape (games, wins, win rate, sorted most-games-first). It names the sibling it is not (opendota_hero_items for plain purchase counts), so an agent can disambiguate without opening either schema.

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?

It states the three mutually exclusive kind values and which filters belong to each ('filters that do not match the kind are rejected'), and explicitly routes the agent to opendota_hero_items when it only wants purchase counts. The when-not and the alternative are both spelled out.

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?