Retrieve a Steam user's owned games with total and recent playtime, sortable by playtime or name.
List the games a user owns, with total and recent hours played.
| Name | Required | Description | Default |
|---|---|---|---|
| params | Yes |
Changes observed during successful MCP inspections.
v1.18.0Input schema / $defs / OwnedGamesInput / properties / include_free_games / titleRemoved value: -"Include Free Games"Input schema / $defs / OwnedGamesInput / properties / limit / titleRemoved value: -"Limit"Input schema / $defs / OwnedGamesInput / properties / offset / titleRemoved value: -"Offset"Input schema / $defs / OwnedGamesInput / properties / response_format / $refRemoved value: -"#/$defs/ResponseFormat"Input schema / $defs / OwnedGamesInput / properties / response_format / enumAdded value: +[
+ "markdown",
+ "json"
+]Input schema / $defs / OwnedGamesInput / properties / response_format / typeAdded value: +"string"Input schema / $defs / OwnedGamesInput / properties / sort_by / titleRemoved value: -"Sort By"Input schema / $defs / OwnedGamesInput / properties / steamid / defaultRemoved value: -nullInput schema / $defs / OwnedGamesInput / properties / steamid / titleRemoved value: -"Steamid"Input schema / $defs / OwnedGamesInput / titleRemoved value: -"OwnedGamesInput"Input schema / $defs / ResponseFormatRemoved value: -{
- "description": "Output format for tool responses.",
- "enum": [
- "markdown",
- "json"
- ],
- "title": "ResponseFormat",
- "type": "string"
-}Input schema / titleRemoved value: -"steam_get_owned_gamesArguments"Output schema / (root)Previous value: -{
- "properties": {
- "result": {
- "title": "Result",
- "type": "string"
- }
- },
- "required": [
- "result"
- ],
- "title": "steam_get_owned_gamesOutput",
- "type": "object"
-}New value: +nullv1.14.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the return detail of 'total and recent hours played', which is useful but not extensive. No mention of rate limits, errors, or what happens when steamid is omitted, but that is partially covered by the schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence with zero waste. The core purpose is front-loaded, and the return details are appended without fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only listing tool with no output schema, the description covers the essential purpose and return fields. Pagination and sorting defaults are documented in the schema, so nothing critical is missing for an agent to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema provides detailed descriptions for all six parameters (limit, offset, sort_by, steamid, response_format, include_free_games), giving high schema coverage. The tool description adds minimal parameter context beyond the return fields, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('List') and resource ('games a user owns') and adds return detail ('total and recent hours played'). It is clear but does not explicitly distinguish from the sibling steam_get_recently_played_games, which overlaps in scope; the distinction is implied by the word 'owns'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternatives like steam_get_recently_played_games or steam_get_wishlist. The purpose is clear enough to infer usage, but the description provides no exclusions or alternative routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.