Skip to main content
Glama
Sarg338

Steam MCP

by Sarg338
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

steam_get_player_summary

Read-only

Retrieve profile details and current activity for multiple Steam users by ID, vanity name, or URL.

Instructions

Get profile + current status for one or more Steam users.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.18.0
    • removedInput schema / $defs / PlayersInput / properties / response_format / $ref
      Removed value: -"#/$defs/ResponseFormat"
    • addedInput schema / $defs / PlayersInput / properties / response_format / enum
      Added value: +[
+  "markdown",
+  "json"
+]
    • addedInput schema / $defs / PlayersInput / properties / response_format / type
      Added value: +"string"
    • removedInput schema / $defs / PlayersInput / properties / steamids / title
      Removed value: -"Steamids"
    • removedInput schema / $defs / PlayersInput / title
      Removed value: -"PlayersInput"
    • 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_summaryArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "steam_get_player_summaryOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.14.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description says 'Get', so it is consistent. The description adds slight behavioral context by noting it supports multiple users at once, but it does not disclose rate limits, privacy handling, or vanity URL expansion.

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 filler. It front-loads the action and resource.

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

Completeness4/5

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

For a simple read-only tool with a detailed schema and readOnlyHint annotation, this description provides sufficient context for invocation. It lacks guidance on return values or edge cases such as private profiles or rate limits, but the schema fills in identifier and format details.

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 description does not add parameter semantics beyond the input schema, which already documents steamids as a list of SteamID64/vanity/profile URLs (max 100) and response_format with markdown/json. Given the schema provides this information, the lack of param details in the description is acceptable, but it adds no extra meaning.

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 clear verb ('Get'), names the resource ('profile + current status'), and specifies scope ('one or more Steam users'). This distinguishes it from sibling user-related tools like steam_get_player_bans or steam_get_friend_list, which target different specific data.

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?

No explicit when-to-use or alternative routing is given. However, the description implies it is the tool for retrieving a player's profile and current online status, but it does not name alternatives or exclusion conditions, so guidance is only implied.

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