Skip to main content
Glama
Sarg338

Steam MCP

by Sarg338
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

steam_get_workshop_item

Read-only

Fetch metadata for a Steam Workshop item using its published file ID. Supports mods, maps, guides, and collections, returning details in markdown or JSON.

Instructions

Get metadata for a Steam Workshop item (mod, map, guide, collection, …).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.18.0
    • removedInput schema / $defs / ResponseFormat
      Removed value: -{
-  "description": "Output format for tool responses.",
-  "enum": [
-    "markdown",
-    "json"
-  ],
-  "title": "ResponseFormat",
-  "type": "string"
-}
    • removedInput schema / $defs / WorkshopItemInput / properties / published_file_id / title
      Removed value: -"Published File Id"
    • removedInput schema / $defs / WorkshopItemInput / properties / response_format / $ref
      Removed value: -"#/$defs/ResponseFormat"
    • addedInput schema / $defs / WorkshopItemInput / properties / response_format / enum
      Added value: +[
+  "markdown",
+  "json"
+]
    • addedInput schema / $defs / WorkshopItemInput / properties / response_format / type
      Added value: +"string"
    • removedInput schema / $defs / WorkshopItemInput / title
      Removed value: -"WorkshopItemInput"
    • removedInput schema / title
      Removed value: -"steam_get_workshop_itemArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "steam_get_workshop_itemOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.14.0

TDQS

A3.7/5.0
Behavior3/5

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

The readOnlyHint=true annotation already covers the safety profile, and the description's 'Get metadata' phrasing is consistent with it. Beyond that, the description adds only scope examples (mod, map, guide, collection) rather than behavioral details such as return shape, markdown-vs-json behavior, failure modes, or rate limits. Consistent but thin, with the annotation lowering the burden.

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?

A single front-loaded sentence: the verb and resource appear first, and the parenthetical item-type list earns its place by disambiguating scope. There is no fluff, redundancy, or restatement of the tool name.

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 lookup with one required parameter, the description covers purpose and scope adequately. Gaps remain: it never mentions the response_format option, what fields 'metadata' includes, or the output shape — and with no output schema present, the description carries that burden and comes up short.

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?

With schema description coverage reported at 0%, the description partially compensates by clarifying the domain of published_file_id through item-type examples (mod, map, guide, collection). However, it adds nothing about the response_format parameter (markdown/json enum) or the ID format, leaving the optional parameter entirely unexplained by the description.

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 specific verb-resource pair: 'Get metadata for a Steam Workshop item', with clarifying examples of item types (mod, map, guide, collection). Among ~40 steam_* siblings, this is the only Workshop-related tool, so the description cleanly differentiates it from steam_get_app_details, steam_get_game_schema, and the player-focused getters.

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?

Usage context is implied by the exclusive Workshop scope — an agent needing an item's metadata can infer this tool is the right choice — but there is no explicit when-to-use guidance, no named alternatives, and no exclusions (e.g., no pointer to steam_get_app_details for app metadata or notes on when not to use it).

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