MCP Dota 2 Match Analysis Server

get_leagues

Fetch all Dota 2 leagues and tournaments. Filter results by tier to narrow down to specific competition levels.

Instructions

Get all Dota 2 leagues/tournaments.

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": "get_leagues"
  }
}

Input Schema

Name	Required	Description	Default
`tier`	No

Output Schema

Name	Required	Description	Default
`error`	No
`leagues`	No
`success`	Yes
`total_leagues`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Jul 31, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the primary function without disclosing pagination, filtering behavior, rate limits, or any other behavioral traits. A read operation is implied, but no safety or side-effect information is given.

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?

The description is a single, front-loaded sentence with no redundant words. It is concise and easy to parse, though it sacrifices completeness for brevity.

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

Completeness2/5

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

Although the tool is simple and has an output schema, the description fails to explain the optional 'tier' parameter or provide any usage context. The complete lack of guidance on how to use the tool or what to expect makes it insufficient for reliable invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has an optional 'tier' parameter, but the description does not explain what 'tier' means, what values it accepts, or how it filters results. With 0% schema description coverage, this is a critical omission.

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?

The description 'Get all Dota 2 leagues/tournaments' uses a specific verb and resource, clearly distinguishing it from siblings like get_league_matches or get_tournament_series that operate on a single league or series. The phrase 'all' also signals a list operation.

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?

There is no guidance on when to use this tool versus alternatives, no mention of prerequisites, and no indication of what scenario it serves. The agent must rely solely on the name.

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