Skip to main content
Glama
Sarg338

Steam MCP

by Sarg338
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

steam_get_player_bans

Read-only

Check a player's VAC, game, community, and economy ban status using their SteamID64, vanity name, or profile URL to quickly identify account restrictions.

Instructions

Get VAC / game / community / economy ban status for a user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.18.0
    • removedInput schema / $defs / PlayerInput / properties / response_format / $ref
      Removed value: -"#/$defs/ResponseFormat"
    • addedInput schema / $defs / PlayerInput / properties / response_format / enum
      Added value: +[
+  "markdown",
+  "json"
+]
    • addedInput schema / $defs / PlayerInput / properties / response_format / type
      Added value: +"string"
    • removedInput schema / $defs / PlayerInput / properties / steamid / default
      Removed value: -null
    • removedInput schema / $defs / PlayerInput / properties / steamid / title
      Removed value: -"Steamid"
    • removedInput schema / $defs / PlayerInput / title
      Removed value: -"PlayerInput"
    • removedInput schema / $defs / ResponseFormat
      Removed value: -{
-  "description": "Output format for tool responses.",
-  "enum": [
-    "markdown",
-    "json"
-  ],
-  "title": "ResponseFormat",
-  "type": "string"
-}
    • removedInput schema / title
      Removed value: -"steam_get_player_bansArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "steam_get_player_bansOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.14.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description is not required to restate safety. It adds the specific ban categories covered, but it does not disclose behavior for invalid steamids, rate limits, or the exact return structure. The added detail is useful but modest, so a mid-range score is appropriate.

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 of ten words, front-loaded with the verb and resource. Every word contributes meaning, and there is no redundancy or filler. It is an exemplary model of concise writing for a tool description.

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?

With no output schema, no mention of response_format, and no parameter details in the description, an agent lacks essential information about how to format the request and what the response contains. The description is too terse to support correct invocation beyond the simplest scenario.

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?

Schema description coverage is 0%, and the description does not mention the required steamid parameter or the response_format parameter. It only says 'for a user', forcing the agent to inspect the schema to learn how to specify the user. The description fails to compensate for the low coverage.

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 names a specific resource (ban status) and enumerates the ban categories (VAC/game/community/economy), which clearly distinguishes it from sibling tools like steam_get_player_summary or steam_get_player_achievements. The verb 'Get' and resource are explicit, leaving no ambiguity about what the tool does.

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 description implies the tool should be used when ban status is needed, but it provides no explicit when-to-use or when-not-to-use guidance and does not reference any sibling tools. An agent can infer its purpose from the wording, but there is no routing or exclusion advice.

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