MCP Dota 2 Match Analysis Server

get_team

Need to know a Dota 2 team's details? Retrieve comprehensive team information by submitting its team ID.

Instructions

Get detailed information about a team by ID.

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": {
      "team_id": "<team_id>"
    },
    "name": "get_team"
  }
}

Input Schema

Name	Required	Description	Default
`team_id`	Yes

Output Schema

Name	Required	Description	Default
`team`	No
`error`	No
`roster`	No
`success`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Jul 31, 2026

TDQS

A3.5/5.0

Behavior2/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 does not state whether the operation is read-only, what happens when the team ID is not found, or any error behavior. The phrase 'detailed information' is vague and lacks concrete expectations beyond the output schema.

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, concise sentence with no redundant information. It is front-loaded with the intent and contains only the necessary details.

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 simplicity of the tool (one parameter) and the presence of an output schema, the description covers the core function. However, it lacks usage guidelines and explicit behavioral expectations, which are important context for an agent deciding when to invoke this tool.

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 input schema has 0% description coverage, so the description must compensate. It does clarify that the parameter is the team identifier ('by ID'), but it does not explain how to obtain this ID or any format constraints beyond the schema's integer type. The parameter name itself is reasonably self-explanatory.

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 clearly states the action (get), the resource (team), and the method (by ID). It effectively distinguishes itself from siblings like search_team and get_team_by_name which have different lookup mechanisms.

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?

The phrase 'by ID' implies that it should be used when a team ID is already known, but no explicit guidance is given on when to use alternatives like search_team or get_team_by_name. This is a minimal but present usage hint.

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