Skip to main content
Glama
Sports Hub MCP Server

Sports Hub MCP Server

by danmorris27

opendota: Get player matches

opendota_get_player_matches
Read-onlyIdempotent

Fetch a player's recent Dota 2 matches with hero, result, K/D/A, and duration; use an optional limit to cap the returned list.

Instructions

Get a player's recent matches (hero, result, K/D/A, duration). Use limit to cap the list.

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": {
      "account_id": "<account_id>"
    },
    "name": "opendota_get_player_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax matches (default 20)
fieldsNoKeys to keep (comma-separated).
account_idYesSteam32 account id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint), so the description only needs to add context. It contributes the fact that results are 'recent' matches with a specific field set, but says nothing about ordering, pagination behavior beyond the cap, or how far back 'recent' reaches.

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 compact sentence plus a short second sentence; the core purpose is front-loaded and nothing is padded. The second sentence is close to duplicating the schema's limit description, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter list tool with no output schema, the description gives a useful field preview but omits ordering (most recent first?), the meaning of 'recent', and how the fields parameter changes the response. Adequate but with visible gaps.

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 all three parameters are documented in the schema itself, including the default of 20 and the min/max on limit. The description's note about using limit to cap the list merely restates the schema and says nothing about the fields or account_id parameters.

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 ('Get a player's recent matches') and previews the returned fields (hero, result, K/D/A, duration), which makes it distinguishable from generic siblings like opendota_get_player or opendota_get_match. It does not, however, explicitly contrast itself with the other player-scoped siblings such as opendota_get_player_heroes or opendota_get_player_win_loss.

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?

The only directive is 'Use `limit` to cap the list', which is parameter usage rather than tool-selection guidance. There is no statement of when this tool is preferable to opendota_get_player, opendota_get_player_heroes, or opendota_get_match, and no prerequisites or exclusions are given.

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

Deploy Server

Other Tools