steam-mcp

get_player_bans

Read-onlyIdempotent

Retrieve a player's VAC, game, economy, and community ban status to assess trustworthiness for reputation checks. Requires an API key.

Instructions

Check a player's VAC, game, economy, and community ban status.

Useful for trust/reputation questions. Requires an API key.

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": {
      "steam_id": "<steam_id>"
    },
    "name": "get_player_bans"
  }
}

Input Schema

Name	Required	Description	Default
`steam_id`	Yes	A Steam account, in any form: a 17-digit SteamID64 (e.g. '76561197960287930'), a STEAM_1:0:11101 or [U:1:22202] id, a full profile URL, or a custom/vanity URL name (e.g. 'gabelogannewell').

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 23, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is well-covered. The description adds useful context by specifying the ban categories and the API key requirement, but it does not describe error behavior, rate limits, or how ban results are structured; the output schema covers the return structure.

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 short sentences deliver the core purpose, the practical use case, and a critical prerequisite (API key). There is no filler or repetition of schema information, so every sentence earns its place.

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

Completeness5/5

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

For a single-parameter, read-only tool with a rich input schema, strong safety annotations, and an output schema, the description provides all necessary selection context: what it checks, when it is useful, and what authentication is required. Nothing essential is missing.

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 provides 100% coverage for the single parameter, including multiple formats, examples, and a thorough description of accepted Steam ID forms. The tool description adds no parameter-level detail, so it does not need to compensate for schema gaps.

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 uses a specific verb ('Check') and a precise resource (a player's VAC, game, economy, and community ban status), which clearly distinguishes it from sibling tools like get_player_summary or get_steam_level. It states exactly what information the tool retrieves.

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?

The description gives clear context ('Useful for trust/reputation questions') that helps an agent decide when to invoke it. It does not explicitly name sibling alternatives or state when not to use it, but the use-case guidance is sufficient for most selection scenarios.

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

Deploy Server