Skip to main content
Glama
Sign In

Opendota

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Pro Matches

pro_matches
Read-onlyIdempotent

Recent professional Dota 2 matches: teams, league, winner, score and duration. OpenDota keyless data.

Input Schema

NameRequiredDescriptionDefault
limitNoMax matches to return (default 20, max 100).
_apiKeyNoOptional — your own OpenDota API key (free, from https://www.opendota.com/api-keys) for higher, PER-KEY rate limits. The endpoint is keyless: omit this and calls still work, but OpenDota rate-limits by calling IP and the shared Worker egress IP is frequently already at quota from unrelated traffic — a caller-supplied key escapes that.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / _apiKey
      Added value: +{
+  "description": "Optional — your own OpenDota API key (free, from https://www.opendota.com/api-keys) for higher, PER-KEY rate limits. The endpoint is keyless: omit this and calls still work, but OpenDota rate-limits by calling IP and the shared Worker egress IP is frequently already at quota from unrelated traffic — a caller-supplied key escapes that.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 20
+  }
+]
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds the data provenance ('OpenDota keyless data'), which hints at reliability/rate-limit behaviour, but says nothing about the rate limits, quotas or pagination that the schema's _apiKey note alludes to.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact clauses, zero filler, with the resource scope and the returned field list front-loaded. Every word carries information.

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 no output schema, the field enumeration (teams, league, winner, score, duration) usefully previews the return shape, and annotations cover safety. It stops short of explaining what 'recent' means, result ordering, or that the limit parameter controls volume, but it is close to sufficient for a simple read-only list tool.

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% with only two parameters, both fully documented in the schema, including the rate-limit rationale for _apiKey. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 resource and scope ('Recent professional Dota 2 matches') plus the returned fields (teams, league, winner, score, duration), which is far more informative than the title 'Pro Matches'. It does not name or differentiate against any sibling, though the resource itself is distinct from get_player/hero_stats/search_players.

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

Usage Guidelines2/5

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

No indication of when to choose this over alternatives, no preconditions, and no note on how 'recent' is bounded or how results are ordered. The agent must infer usage purely from the resource name.

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

All Opendota 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