Skip to main content
Glama
Sarg338

Steam MCP

by Sarg338
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

steam_get_recently_played_games

Read-only

Retrieve a Steam user's recently played games from the last two weeks, including playtime hours. Accepts SteamID64, vanity name, or full profile URL.

Instructions

List games a user has played in the last two weeks, with hours.

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_recently_played_gamesArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "steam_get_recently_played_gamesOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.14.0

TDQS

B3.4/5.0
Behavior3/5

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

The readOnlyHint annotation already signals that this is a safe read operation, and the description's 'List' is consistent. The description adds no extra behavioral context beyond that, such as rate limits, authentication requirements, or what happens if steamid is omitted (though the schema mentions defaulting to configured user). It is adequate but minimal given the annotation coverage.

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, front-loaded sentence with zero redundancy. It communicates the core purpose and output in the most efficient way possible.

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?

For a simple read-only tool, the description covers the basic purpose and hints at the output ('with hours'), but it does not explain the full return structure, the optional nature of steamid, or the response_format option. Since there is no output schema, the description could provide more detail about what the agent will receive. It is minimally adequate but leaves gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is reported as 0% for the top-level params, and the description does not mention any parameters. It says 'a user' but does not explain how the user is specified or that the response_format parameter exists. The nested schema descriptions for steamid and response_format provide some detail, but the description fails to compensate for the low coverage and adds no parameter guidance.

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 states a clear verb ('List'), a specific resource ('games a user has played'), a time scope ('last two weeks'), and an output detail ('with hours'). It clearly distinguishes from sibling tools like steam_get_owned_games (which lists all owned games) and steam_get_player_summary (which summarizes player info).

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention any exclusion criteria, alternatives, or contextual conditions. An agent must infer that this is for recent play history, but there is no explicit routing guidance among the 40+ siblings.

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