Retrieve any Steam user's inventory items by SteamID or profile URL. Filter by app (Community items, CS2, TF2, Dota 2) and limit results for a targeted read.
List a user's Steam inventory — game items or generic Community items.
| Name | Required | Description | Default |
|---|---|---|---|
| params | Yes |
Changes observed during successful MCP inspections.
v1.18.0Input schema / $defs / InventoryInput / properties / appid / titleRemoved value: -"Appid"Input schema / $defs / InventoryInput / properties / context_id / defaultRemoved value: -nullInput schema / $defs / InventoryInput / properties / context_id / titleRemoved value: -"Context Id"Input schema / $defs / InventoryInput / properties / count / titleRemoved value: -"Count"Input schema / $defs / InventoryInput / properties / language / titleRemoved value: -"Language"Input schema / $defs / InventoryInput / properties / limitAdded value: +{
+ "default": 50,
+ "description": "Max distinct items to list, most-numerous first (1-200); distinct_items always counts all of them.",
+ "maximum": 200,
+ "minimum": 1,
+ "type": "integer"
+}Input schema / $defs / InventoryInput / properties / response_format / $refRemoved value: -"#/$defs/ResponseFormat"Input schema / $defs / InventoryInput / properties / response_format / enumAdded value: +[
+ "markdown",
+ "json"
+]Input schema / $defs / InventoryInput / properties / response_format / typeAdded value: +"string"Input schema / $defs / InventoryInput / properties / steamid / defaultRemoved value: -nullInput schema / $defs / InventoryInput / properties / steamid / titleRemoved value: -"Steamid"Input schema / $defs / InventoryInput / titleRemoved value: -"InventoryInput"Input schema / $defs / ResponseFormatRemoved value: -{
- "description": "Output format for tool responses.",
- "enum": [
- "markdown",
- "json"
- ],
- "title": "ResponseFormat",
- "type": "string"
-}Input schema / titleRemoved value: -"steam_get_inventoryArguments"Output schema / (root)Previous value: -{
- "properties": {
- "result": {
- "title": "Result",
- "type": "string"
- }
- },
- "required": [
- "result"
- ],
- "title": "steam_get_inventoryOutput",
- "type": "object"
-}New value: +nullv1.14.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already conveys that this is a safe read operation, and the description is consistent with that. However, the description adds little beyond the annotation—only noting the two item types. It does not disclose sampling behavior, pagination, or the configurable defaults, which could affect user expectations. Since the annotation covers the core safety aspect, a 3 is acceptable but not standout.
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?
The description is a single, well-structured sentence that states the core purpose concisely. It is front-loaded and has no filler. The only reason not to give a 5 is that it omits any hint at additional behavior or parameters, but as a pure purpose statement it is both concise and effective.
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?
The tool has seven parameters, no output schema, and the description only covers the bare purpose. It does not explain that output can be markdown or json, that large inventories are sampled rather than fully retrieved, or that default behaviors exist. For a tool with this complexity, the description is incomplete and leaves the agent without important context about what to expect from the tool's execution.
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 description does not mention any parameters, and the context signal indicates 0% coverage of parameters in the description. However, the input schema itself provides extensive descriptions for all seven parameters (appid, count, limit, steamid, language, context_id, response_format), so the schema carries full semantic weight. Per the rubric, baseline 3 is appropriate when the schema is rich and the description adds no redundant detail.
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 clearly identifies the action ('List') and the resource ('a user's Steam inventory'), and additionally distinguishes between the two item categories (game items or generic Community items). This is specific and unambiguous, and no sibling tool appears to overlap with this functionality, so no extra differentiation is needed.
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?
The description provides no guidance on when to use this tool versus alternatives. It does not mention any conditions, prerequisites, or mention that it should be used for inventory queries specifically. The agent is left to infer usage solely from the tool name and description, which is insufficient for a tool with many siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.