MCP Dota 2 Match Analysis Server

get_cs_at_minute

Get last hits, denies, gold, and level for all heroes at a given minute to assess individual performance during any phase of a Dota 2 match.

Instructions

Get last hits, denies, gold, and level for all heroes at a specific minute.

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": {
      "match_id": "<match_id>",
      "minute": "<minute>"
    },
    "name": "get_cs_at_minute"
  }
}

Input Schema

Name	Required	Description	Default
`minute`	Yes
`match_id`	Yes

Output Schema

Name	Required	Description
`error`	No
`heroes`	No
`minute`	No	Game minute
`success`	Yes
`match_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Jul 31, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It accurately describes a read-only retrieval but does not mention potential error conditions, rate limits, or assumptions about match_id or minute validity.

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?

The description is a single sentence that is front-loaded with the main verb and content, containing no redundant or extraneous words.

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?

Given the tool's simplicity and the existence of an output schema, the description covers the core purpose. However, it lacks usage guidance, sibling differentiation, and any behavioral caveats, making it moderately complete.

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?

The schema defines two integer parameters (match_id, minute) with 0% coverage from the description. The description adds meaning by explaining the minute dimension ('at a specific minute'), but leaves match_id implicit and does not clarify valid ranges or format.

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?

The description clearly states the tool retrieves last hits, denies, gold, and level for all heroes at a specific minute. It is specific about the resource but does not explicitly differentiate from sibling tools like get_stats_at_minute or get_snapshot_at_time.

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 guidance is provided on when to use this tool versus alternatives such as get_stats_at_minute. There is no mention of preferred contexts, exclusions, or prerequisites.

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