Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

opendota_hero_matches

Read-only

Returns about 100 recent professional and public Dota 2 matches in which a hero was played: side, win or loss, kills, deaths, assists, duration and league when there is one; account ids are omitted. Provide hero_id from opendota_heroes; unknown ids return not found.

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_hero_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
hero_idYesRequired positive hero ID from opendota_heroes.

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

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnly and openWorld, and the description adds real context beyond them: roughly 100 results, mixing pro and public matches, inclusion of league only when one exists, and deliberate omission of account ids. It stops short of saying whether results are sorted by recency or how the cap behaves.

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?

One front-loaded sentence covers scope, return fields and omissions, with a short second clause on the parameter and error mode. Dense and waste-free, though the semicolon chain is slightly run-on.

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?

For a one-parameter read tool with an output schema and safety annotations, the description covers result size, scope, field list, omissions and error behavior. Missing only ordering/pagination details, which are minor.

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 parameter is documented structurally; the description nonetheless adds failure semantics (unknown ids return not found) on top of the schema's 'positive hero ID from opendota_heroes', which is genuine added value for the single required param.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: recent professional and public Dota 2 matches in which a given hero was played, and enumerates the returned fields. An agent can distinguish it from general match tools, though it never names nearby siblings such as opendota_find_matches, opendota_hero_matchups or opendota_match explicitly.

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 says to supply hero_id from opendota_heroes and warns unknown ids return not found, which implies the lookup chain but never states when to prefer this over sibling match tools or when it is unsuitable.

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