Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

opendota_records

Read-only

Returns OpenDota's top-100 single-match Dota 2 records for one stat (kills, deaths, assists, last_hits, denies, gold_per_min, xp_per_min, hero_damage, tower_damage, hero_healing or duration): rank, match id, start time, hero with name and the record value. Provide field. Use opendota_match with a returned match id.

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": {
      "field": "<field>"
    },
    "name": "opendota_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldYesRequired record leaderboard: kills, deaths, assists, last_hits, denies, gold_per_min, xp_per_min, hero_damage, tower_damage, hero_healing or duration.

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.1/5.0
Behavior4/5

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

Annotations already cover readOnly and openWorld, so credit goes for added context: the fixed top-100 cap, one stat per call, and the response shape (rank, match id, start time, hero name, value). It doesn't discuss rate limits or caching, which is a minor gap against an already-declared safety profile.

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?

Front-loads the scope and record cap, then the field list, then the follow-up routing in a single tight paragraph. The long parenthetical list is dense but it is load-bearing enumerable values rather than filler.

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?

With a single required param, an output schema, and annotations present, the description supplies the missing pieces: result cardinality (top-100), per-call single-stat semantics, and the downstream match lookup. Complete enough to call correctly.

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 schema description already enumerates the exact allowed stat values verbatim. The description repeats that same list plus the field name, adding little semantic value beyond the schema; 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 (Returns) plus a precise resource scope: OpenDota's top-100 single-match records for one stat, and enumerates the stat options. An agent can distinguish it from siblings like opendota_match or opendota_benchmarks immediately.

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 names the follow-up path: 'Use opendota_match with a returned match id', and 'Provide field' signals the required argument. It gives clear context but does not state exclusions, e.g. that it returns a fixed top-100 leaderboard rather than arbitrary filters.

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