Skip to main content
Glama
Sports Hub MCP Server

Sports Hub MCP Server

by danmorris27

opendota: Get pro matches

opendota_get_pro_matches
Read-onlyIdempotent

Fetch recent professional Dota 2 matches with teams, league, duration, and winner to monitor results; use a match ID for full detail.

Instructions

Get recent professional Dota 2 matches (teams, league, duration, winner). Use a match_id with opendota_get_match for full detail.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "opendota_get_pro_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds which fields come back, but says nothing about result limits/pagination or how 'recent' is bounded, which matters for a live pro-match feed.

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 sentences, zero filler, and the primary purpose is front-loaded ahead of the sibling pointer. Every clause earns its place.

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-optional-param list endpoint with annotations carrying the safety profile and no output schema, the description is nearly sufficient: it names the resource, the scope, the returned fields, and the sibling alternative. Only the 'recent' window and any result cap are 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 sole optional 'fields' parameter is already documented by the schema. The description adds no syntax, defaults, or projection examples 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.

Purpose5/5

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

States a specific verb and resource ('Get recent professional Dota 2 matches') and even previews the returned fields (teams, league, duration, winner). It explicitly names the sibling opendota_get_match for the detail-view case, so an agent can distinguish the two without opening either schema.

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 routes the detail case: 'Use a match_id with opendota_get_match for full detail,' which tells the agent when to prefer the sibling. It stops short of stating when NOT to use this tool (e.g., no filtering options beyond fields), leaving some inference.

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