Skip to main content
Glama

Opendota

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Players

search_players
Read-onlyIdempotent

Search Dota 2 players by persona (display) name. Returns matching account IDs and similarity scores. OpenDota keyless data; may be empty if rate-limited.

Input Schema

NameRequiredDescriptionDefault
nameYesPersona / display name to search for.
limitNoMax players to return (default 10).
_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": 5,
+    "name": "Arteezy"
+  },
+  {
+    "name": "N0tail"
+  }
+]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the safety profile is covered. The description adds real value beyond them: the keyless OpenDota data source, the rate-limit failure mode ('may be empty if rate-limited'), and the result shape (account IDs plus similarity scores). It does not mention pagination or ordering of results.

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 tight sentences that front-load the purpose, then the return shape and the rate-limit caveat. No filler and nothing buried.

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 description carries the return explanation and does so ('account IDs and similarity scores') plus a failure-mode warning. It is nearly complete for a simple search tool; only result ordering/pagination behavior is unaddressed.

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 schema already documents name, limit, and _apiKey thoroughly. The description restates the name parameter's meaning but adds no format, matching-semantics, or limit guidance beyond what the schema provides — baseline 3.

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 and resource ('Search Dota 2 players by persona name') and what it returns ('matching account IDs and similarity scores'). It is easy to distinguish from get_player by the name-vs-ID lookup, but the description never explicitly names that sibling to sharpen the contrast.

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?

Usage is only implied: an agent infers it should search when it has a display name rather than an account ID. There is no explicit when-to-use, when-not-to-use, or routing to get_player for the ID-based case.

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